Triple
T22334690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curva A |
E552112
|
entity |
| Predicate | standShape |
P4076
|
FINISHED |
| Object | curved stand |
—
|
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: curved stand | Statement: [Curva A, standShape, curved stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standShape Context triple: [Curva A, standShape, curved stand]
-
A.
standStructure
Indicates that one entity is a vertical support or upright structural element for another entity.
-
B.
shaped
chosen
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
C.
stands
Indicates that an entity is in an upright position, typically supported by its feet or base, rather than sitting, lying, or moving.
-
D.
standConfiguration
Indicates that one entity specifies or defines the arrangement, setup, or layout configuration of a stand (e.g., booth, display, or support structure) in relation to another entity.
-
E.
rootShape
Indicates that one entity has the primary or overall geometric form or outline specified by the other entity.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577e35f48190b11789d80182653e |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.