Triple
T20626621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Underground Atlanta |
E506834
|
entity |
| Predicate | openedAsShoppingDistrict |
P4285
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Underground Atlanta, openedAsShoppingDistrict, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsShoppingDistrict Context triple: [Underground Atlanta, openedAsShoppingDistrict, 1969]
-
A.
isShoppingDistrict
Indicates that a location functions primarily as a shopping district, characterized by a concentration of retail stores and commercial shopping activity.
-
B.
hasShoppingDistrict
chosen
Indicates that a place contains or is associated with a designated area where multiple shops and commercial retail activities are concentrated.
-
C.
hasShoppingDistrictName
Indicates that an entity’s shopping district is identified by a specific name.
-
D.
hasShoppingDistrictType
Indicates that an entity is associated with a particular type or category of shopping district.
-
E.
opensShopTo
Indicates that one entity makes a shop accessible or available for another entity, typically by starting or unlocking its operation for them.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6abe576c081909231dc0d7304b9a9 |
completed | April 20, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:42 a.m.