Triple
T25357266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morelia viridis |
E635856
|
entity |
| Predicate | restingPosture |
P42040
|
FINISHED |
| Object | coiled over branches in saddle position |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: coiled over branches in saddle position | Statement: [Morelia viridis, restingPosture, coiled over branches in saddle position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restingPosture Context triple: [Morelia viridis, restingPosture, coiled over branches in saddle position]
-
A.
lieAlong
Indicates that one object or feature is positioned adjacent to and extending in roughly the same direction as another.
-
B.
restingBehavior
Indicates a relationship where an entity is in a state of rest or inactivity, typically pausing movement or action for recovery or idling.
-
C.
describesPosture
chosen
Indicates that one entity specifies or characterizes the bodily position or stance (posture) of another entity.
-
D.
positionDuringSitting
Indicates the spatial position or posture an entity has specifically while it is in a sitting state.
-
E.
laidDown
Indicates that an entity places or sets another entity down into a resting or horizontal position.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49e0263e081909449045f434eac6c |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:36 p.m.