Triple
T26707695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troglodytes troglodytes |
E673324
|
entity |
| Predicate | tailPosition |
P119437
|
FINISHED |
| Object | often held upright |
—
|
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: often held upright | Statement: [Troglodytes troglodytes, tailPosition, often held upright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailPosition Context triple: [Troglodytes troglodytes, tailPosition, often held upright]
-
A.
tailLocation
chosen
Indicates the spatial position or placement of an entity’s tail relative to a reference frame or another object.
-
B.
tailConfiguration
Indicates how the tail of an entity is arranged, structured, or positioned relative to the rest of that entity.
-
C.
leafPosition
Indicates the spatial or structural placement of a leaf relative to its supporting plant organ or axis.
-
D.
positionRelativeToTailrace
Indicates the spatial relationship of an entity’s location with respect to the tailrace (the downstream outflow area of a hydraulic or hydroelectric system).
-
E.
tailSpan
Indicates the length or extent of an entity’s tail, typically measured from its base to its tip.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617bb5a38819099dace3392694896 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:34 a.m.