Triple
T34703875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S33 chair design |
E1000446
|
entity |
| Predicate | hasStructuralPrinciple |
P200923
|
FINISHED |
| Object | cantilevered frame |
—
|
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: cantilevered frame | Statement: [S33 chair design, hasStructuralPrinciple, cantilevered frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructuralPrinciple Context triple: [S33 chair design, hasStructuralPrinciple, cantilevered frame]
-
A.
hasStructuralCharacter
Indicates that one entity possesses a particular structural property, form, or configuration that characterizes it.
-
B.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
C.
hasGoverningPrinciple
Indicates that one entity is guided, regulated, or constrained by a specific principle, rule, or doctrine that governs its behavior or operation.
-
D.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
E.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69ffb97ae1508190bf3addd6e2aac281 |
completed | May 9, 2026, 10:47 p.m. |
Created at: May 3, 2026, 3:59 p.m.