Triple
T24049679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AZCA business district |
E595619
|
entity |
| Predicate | secondaryBuildingUse |
P154671
|
FINISHED |
| Object | retail |
—
|
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: retail | Statement: [AZCA business district, secondaryBuildingUse, retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBuildingUse Context triple: [AZCA business district, secondaryBuildingUse, retail]
-
A.
secondaryLandUse
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
-
B.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
C.
previousBuildingUse
Indicates that a building previously served a specified use or function before its current one.
-
D.
primaryLandUse
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
E.
associatedWithVenueSecondaryUse
Indicates that an entity has a secondary or supplementary association with a particular venue, beyond its primary or main use.
- F. None of above. chosen
Provenance (4 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cfb914819091a3378518f9f28d |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:19 p.m.