Triple
T36146104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liam Digby is mistaken for an adult |
E1045453
|
entity |
| Predicate | involvesPhysicalTrait |
P31173
|
FINISHED |
| Object | unusually tall |
—
|
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: unusually tall | Statement: [Liam Digby is mistaken for an adult, involvesPhysicalTrait, unusually tall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesPhysicalTrait Context triple: [Liam Digby is mistaken for an adult, involvesPhysicalTrait, unusually tall]
-
A.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
B.
causeOfPhysicalTrait
Indicates that one entity is responsible for producing or determining a specific physical characteristic in another entity.
-
C.
hasHumanCharacteristic
Indicates that an entity possesses a trait, quality, or behavior typically associated with humans.
-
D.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
E.
rimCharacteristic
Indicates a specific property or feature that characterizes a rim in the context of its structure, design, or function.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:08 p.m.