Triple
T31209289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcel Breuer and Associates |
E795690
|
entity |
| Predicate | knownForDesignFeature |
P57584
|
FINISHED |
| Object | cantilevered forms |
—
|
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 forms | Statement: [Marcel Breuer and Associates, knownForDesignFeature, cantilevered forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForDesignFeature Context triple: [Marcel Breuer and Associates, knownForDesignFeature, cantilevered forms]
-
A.
designedFeature
chosen
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
B.
testedDesignFeature
Indicates that a specific design feature has been subjected to a test or evaluation process.
-
C.
usedDesignFeature
Indicates that one entity employed or incorporated a particular design feature in its creation, implementation, or functionality.
-
D.
notableTechnicalFeature
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
-
E.
previousDesignFeature
Indicates that one design feature precedes another in a sequence or earlier version of a design.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:09 p.m.