Triple
T14916299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Womb Chair |
E371390
|
entity |
| Predicate | hasBaseFinish |
P49891
|
FINISHED |
| Object | polished chrome |
—
|
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: polished chrome | Statement: [Womb Chair, hasBaseFinish, polished chrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseFinish Context triple: [Womb Chair, hasBaseFinish, polished chrome]
-
A.
hasFrameFinish
Indicates that an entity’s frame possesses a specific surface treatment or finish.
-
B.
baseFinish
chosen
Indicates that one entity serves as the foundational or underlying finish or surface treatment upon which another finish or treatment is applied or built.
-
C.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
D.
hasFinalState
Indicates that an entity ultimately results in, transitions to, or ends in a specified final state or condition.
-
E.
hasFinalStage
Indicates that an entity possesses or reaches a concluding or ultimate phase in a process, sequence, or lifecycle.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:31 a.m.