Triple
T36766836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaellynasaura |
E908361
|
entity |
| Predicate | sizeEstimate |
P38193
|
FINISHED |
| Object | about 1–2 meters in length |
—
|
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: about 1–2 meters in length | Statement: [Leaellynasaura, sizeEstimate, about 1–2 meters in length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sizeEstimate Context triple: [Leaellynasaura, sizeEstimate, about 1–2 meters in length]
-
A.
heightEstimate
chosen
Indicates an estimated or approximate value for the height of an entity, rather than a precisely measured height.
-
B.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
-
C.
approximateSize
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
D.
librarySizeApprox
Indicates that the size of a library (e.g., number of items, capacity, or volume) is known or treated as an approximate value rather than an exact measurement.
-
E.
sizeDescription
Indicates a relationship where one entity provides descriptive information about the size or scale of another entity.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.