Triple
T26810857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ionic order |
E671987
|
entity |
| Predicate | typicalLocationOnBuilding |
P143279
|
FINISHED |
| Object | upper stories |
—
|
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: upper stories | Statement: [Ionic order, typicalLocationOnBuilding, upper stories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationOnBuilding Context triple: [Ionic order, typicalLocationOnBuilding, upper stories]
-
A.
locatedOnBuilding
Indicates that one entity is physically situated on the exterior or rooftop surface of a building.
-
B.
locationInArchitecture
chosen
Indicates the spatial position or placement of one architectural element or feature within or relative to another architectural structure or context.
-
C.
oftenLocatedAt
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
D.
emblematicBuildingLocation
Indicates that a building serves as a symbolic or representative landmark for a particular location or area.
-
E.
seatBuildingLocatedIn
Indicates that the building serving as a seat (e.g., headquarters or main office) is geographically located within a specified area or place.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: April 27, 2026, 4:29 a.m.