Triple
T38654510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diplodocoidea |
E939851
|
entity |
| Predicate | neckPostureHypothesis |
P42040
|
FINISHED |
| Object | adapted for wide lateral sweep feeding |
—
|
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: adapted for wide lateral sweep feeding | Statement: [Diplodocoidea, neckPostureHypothesis, adapted for wide lateral sweep feeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckPostureHypothesis Context triple: [Diplodocoidea, neckPostureHypothesis, adapted for wide lateral sweep feeding]
-
A.
neckRelativeToBody
Indicates the spatial or anatomical position and orientation of a neck in relation to the main body.
-
B.
headMobility
Indicates the degree to which an entity’s head can move or be moved relative to its body.
-
C.
describesPosture
chosen
Indicates that one entity specifies or characterizes the bodily position or stance (posture) of another entity.
-
D.
neckJoint
Indicates a joint or connection located at or functioning as the neck between two body parts or structural elements.
-
E.
headStatus
Indicates the current condition, role, or state of an entity in its capacity as a head or leader within a given context.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:33 p.m.