Triple
T35063534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIT College of Architecture |
E1011664
|
entity |
| Predicate | usesBuildingDesignedBy |
P184
|
FINISHED |
| Object | Ludwig Mies van der Rohe |
—
|
NE NERFINISHED |
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: Ludwig Mies van der Rohe | Statement: [IIT College of Architecture, usesBuildingDesignedBy, Ludwig Mies van der Rohe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBuildingDesignedBy Context triple: [IIT College of Architecture, usesBuildingDesignedBy, Ludwig Mies van der Rohe]
-
A.
isArchitectDesigned
Indicates that something was created or planned by a professional architect.
-
B.
currentBuildingDesignedBy
Indicates that the building currently associated with an entity was designed by a specified architect or designer.
-
C.
designedBy
chosen
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
D.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
E.
architectOfCommissionedBuilding
Indicates that a person served as the architect responsible for designing a building that was specifically commissioned.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7860f24c4819081e8e61621d36a69 |
completed | May 3, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.