Triple
T26868699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrannosauroidea |
E676543
|
entity |
| Predicate | bodySizeTrend |
P60169
|
FINISHED |
| Object | large-bodied in derived forms |
—
|
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-bodied in derived forms | Statement: [Tyrannosauroidea, bodySizeTrend, large-bodied in derived forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodySizeTrend Context triple: [Tyrannosauroidea, bodySizeTrend, large-bodied in derived forms]
-
A.
sizeTrend
chosen
Indicates how the size of an entity changes over time or relative to another entity (e.g., increasing, decreasing, or remaining stable).
-
B.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
C.
sizeStatus
Indicates the relative size condition or classification of one entity in relation to another or to a defined standard.
-
D.
weightSize
Indicates a relationship between an entity’s weight and its physical size, typically expressing how one varies or is characterized in terms of the other.
-
E.
sizeCategory
Indicates the relative size classification assigned to an entity compared to others (e.g., small, medium, large).
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e99f138819097659bf61b6b35c2 |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:30 a.m.