Triple
T7820101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iguanodon fossils |
E181105
|
entity |
| Predicate | anatomicalEvidenceFor |
P3650
|
FINISHED |
| Object | facultative bipedalism |
—
|
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: facultative bipedalism | Statement: [Iguanodon fossils, anatomicalEvidenceFor, facultative bipedalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anatomicalEvidenceFor Context triple: [Iguanodon fossils, anatomicalEvidenceFor, facultative bipedalism]
-
A.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
B.
providesEvidenceFor
chosen
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
C.
affectsAnatomicalLocation
Indicates that one entity produces an effect on, or has an impact at, a specific anatomical location.
-
D.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
E.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa06d28881908d62d4c02b45cedd |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:41 p.m.