Triple
T36766847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaellynasaura |
E908361
|
entity |
| Predicate | eyeSizeRelativeToSkull |
P186276
|
FINISHED |
| Object | large |
—
|
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: large | Statement: [Leaellynasaura, eyeSizeRelativeToSkull, large]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eyeSizeRelativeToSkull Context triple: [Leaellynasaura, eyeSizeRelativeToSkull, large]
-
A.
eyeToBodySizeRatio
Indicates the proportional relationship between the size of an entity's eye and the overall size of its body.
-
B.
oculusDiameter
Indicates the diameter measurement of an oculus (a circular opening), relating the opening to the size of its circular span.
-
C.
hasCranialCapacity
Indicates that one entity possesses a specific volume or size of space within the skull available for the brain.
-
D.
cranialCapacity
Indicates the volume or size of the interior space of the skull that can house the brain.
-
E.
headProportion
Indicates the proportional relationship between the size of an entity’s head and a reference measure, such as its body or overall height.
- F. None of above. chosen
Provenance (4 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.