Triple
T3603872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tulip chair |
E76322
|
entity |
| Predicate | baseFinish |
P49891
|
FINISHED |
| Object | painted to match seat shell in many versions |
—
|
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: painted to match seat shell in many versions | Statement: [Tulip chair, baseFinish, painted to match seat shell in many versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseFinish Context triple: [Tulip chair, baseFinish, painted to match seat shell in many versions]
-
A.
bodyFinish
Indicates that one entity completes or finishes the main body or primary portion of another entity.
-
B.
startFinishType
Indicates the specific way in which an activity, event, or process begins and/or ends (e.g., its initiation and completion characteristics).
-
C.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
D.
startFinishArea
Indicates a relationship where a defined area serves as both the starting point and the finishing point for an event, route, or activity.
-
E.
finishingArea
Indicates the location or area where an activity, process, or event comes to an end or is completed.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc1e07bc481908d9fce18d36d8e0d |
completed | March 8, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.