Triple
T8732250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cesca Chair |
E207284
|
entity |
| Predicate | hasTypicalFinish |
P84337
|
FINISHED |
| Object | chromed steel |
—
|
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: chromed steel | Statement: [Cesca Chair, hasTypicalFinish, chromed steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalFinish Context triple: [Cesca Chair, hasTypicalFinish, chromed steel]
-
A.
typicalFinish
Indicates that an action, process, or event commonly or characteristically ends with a particular outcome or state.
-
B.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
C.
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.
-
D.
hasSprintFinish
Indicates that an event, activity, or process concludes with a short, intense final effort or burst of speed.
-
E.
finisher
Indicates that an entity completes, concludes, or brings to an end a process, event, or sequence, often as the final actor or decisive contributor.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d2903b08190a5ef29b6d6ca5f1c |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:37 p.m.