Triple
T21674342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tele |
E534928
|
entity |
| Predicate | hasCommonFinish |
P145392
|
FINISHED |
| Object | butterscotch blonde |
—
|
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: butterscotch blonde | Statement: [Tele, hasCommonFinish, butterscotch blonde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonFinish Context triple: [Tele, hasCommonFinish, butterscotch blonde]
-
A.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
B.
canBeFinishedAs
Indicates that one entity (such as a task, process, or activity) is capable of being completed or brought to an end in the form or manner specified by another entity.
-
C.
hasFrameFinish
Indicates that an entity’s frame possesses a specific surface treatment or finish.
-
D.
hasStartFinishOn
Indicates that an event, process, or activity begins and ends on a specified time, date, or boundary.
-
E.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a0ed5388190b8f1932fb3f11c6a |
completed | April 27, 2026, 4:08 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69cb4bcbc8190a4fc2d508df107be |
completed | April 20, 2026, 9:37 p.m. |
Created at: April 16, 2026, 6:41 p.m.