Triple
T17644042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masonic Temple Detroit (nearby area) |
E429309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | area surrounding landmark |
C38371
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: area surrounding landmark Context triple: [Masonic Temple Detroit (nearby area), instanceOf, area surrounding landmark]
-
A.
vicinity of a geographic feature
chosen
The "vicinity of a geographic feature" represents the surrounding area within a defined or implied distance of a specific natural or man-made geographic element, such as a mountain, river, or building.
-
B.
tourist attraction area
A tourist attraction area is a designated geographic location that offers notable natural, cultural, historical, or recreational features and supporting facilities that draw visitors for leisure, education, or entertainment.
-
C.
navigation infrastructure vicinity
Navigation infrastructure vicinity is the spatial region surrounding navigational aids or facilities (such as beacons, buoys, or control towers) within which their presence, signals, or operational constraints are relevant to route planning and movement.
-
D.
campus vicinity
The campus vicinity is the surrounding area adjacent to a campus that includes nearby streets, businesses, residences, and public spaces commonly used by campus members.
-
E.
group of landmarks
A group of landmarks is a collection of notable physical or cultural reference points that are considered together for purposes such as navigation, analysis, or representation.
- F. None of above.
Provenance (1 batch)
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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 6:03 a.m.