Triple
T9943213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clayton, Missouri |
E194133
|
entity |
| Predicate | hasHighRiseOfficeBuildings |
P39751
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Clayton, Missouri, hasHighRiseOfficeBuildings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighRiseOfficeBuildings Context triple: [Clayton, Missouri, hasHighRiseOfficeBuildings, true]
-
A.
isHighRise
Indicates that a building or structure is classified as a high-rise, typically due to its height exceeding a defined multi-story threshold.
-
B.
hasHighRiseSpan
Indicates that a structure or element extends vertically across a significant number of levels or stories, forming a tall or high-rise span.
-
C.
hasOfficeBuildings
chosen
Indicates that one entity possesses, controls, or is associated with one or more office buildings.
-
D.
isMajorOfficeBuildingIn
Indicates that a building is a primary or significant office structure located within a specified geographic or administrative area.
-
E.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6124a188190b41feadb7b2f8922 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.