Triple
T18972337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchell & Stout Architects |
E464199
|
entity |
| Predicate | focusesOnBuildingType |
P1844
|
FINISHED |
| Object | public buildings |
—
|
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: public buildings | Statement: [Mitchell & Stout Architects, focusesOnBuildingType, public buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnBuildingType Context triple: [Mitchell & Stout Architects, focusesOnBuildingType, public buildings]
-
A.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
-
B.
buildingType
chosen
Indicates the specific category or function that characterizes what kind of building something is.
-
C.
appliedToBuildingType
Indicates that something (such as a rule, measure, or classification) is specifically applicable to a particular type of building.
-
D.
containsBuildingType
Indicates that a location or area includes at least one building of the specified type.
-
E.
originalBuildingType
Indicates the type or category of building that something was initially constructed or designated to be, before any later changes or repurposing.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61cb3ac8190bfe29104166fa090 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon