Triple
T18632791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ant chair |
E455463
|
entity |
| Predicate | originalLegFinish |
P132472
|
FINISHED |
| Object | chrome-plated 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: chrome-plated steel | Statement: [Ant chair, originalLegFinish, chrome-plated steel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLegFinish Context triple: [Ant chair, originalLegFinish, chrome-plated steel]
-
A.
secondLegOrigin
Indicates the location from which the second leg of a multi-leg journey or route begins.
-
B.
firstLeg
Indicates that one entity represents the initial segment or starting portion of a multi-part journey, sequence, or process involving another entity.
-
C.
originalFinale
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
D.
originallyLeggedThrough
Indicates that something was initially routed, transmitted, or processed through a particular intermediary, channel, or pathway before any subsequent changes or re-routing.
-
E.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc5c7ec8190ab0c64f009583f96 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e485f5d1588190b44f31cbc54c0a9d |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 11:46 a.m.