Triple
T17301232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebright Azimuth vicinity |
E420043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vicinity of a geographic feature |
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: vicinity of a geographic feature Context triple: [Ebright Azimuth vicinity, instanceOf, vicinity of a geographic feature]
-
A.
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.
-
B.
location-based feature
A location-based feature is a functionality or attribute of a system that uses a user's geographic position to provide context-aware information, services, or interactions.
-
C.
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.
-
D.
location
A location is a specific place or position in physical or virtual space that can be identified, referenced, and used to describe where entities or events exist or occur.
-
E.
locality
A locality is a geographically bounded area, such as a neighborhood, town, or district, characterized by its specific physical setting, social community, and administrative identity.
- F. None of above. chosen
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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:41 a.m.