Triple
T3886166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duff |
E92945
|
entity |
| Predicate | associatedPhysicalDescription |
P31173
|
FINISHED |
| Object | dark-haired |
—
|
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: dark-haired | Statement: [Duff, associatedPhysicalDescription, dark-haired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPhysicalDescription Context triple: [Duff, associatedPhysicalDescription, dark-haired]
-
A.
hasPhysicalFeature
chosen
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
B.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
C.
associatedBody
Indicates a relationship where one entity is linked or connected to another entity as its related or corresponding body.
-
D.
appearance
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
E.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec942bfc8190a398fe370715a28b |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.