Triple
T3414887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM SIGSPATIAL International Conference on Advances in Geographic Information Systems |
E71986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographic information systems conference |
C11186
|
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: geographic information systems conference Context triple: [ACM SIGSPATIAL International Conference on Advances in Geographic Information Systems, instanceOf, geographic information systems conference]
-
A.
geographic markup language
Geographic Markup Language is an XML-based standard for encoding, storing, and exchanging geographic information and spatial features on the web.
-
B.
geographer
A geographer is a professional who studies the Earth's landscapes, environments, and the relationships between people and their spatial surroundings.
-
C.
geography department
A geography department is an academic unit within an educational institution that focuses on the study, research, and teaching of Earth's landscapes, environments, places, and spatial relationships between people and their surroundings.
-
D.
Konferenz
chosen
Eine Konferenz ist eine organisierte, meist zeitlich begrenzte Veranstaltung, bei der mehrere Personen zusammenkommen, um Informationen zu einem bestimmten Thema auszutauschen, zu präsentieren und zu diskutieren.
-
E.
architectural congress
An architectural congress is a formal gathering of architects, planners, scholars, and related professionals convened to discuss, present, and debate ideas, projects, and policies shaping the built environment.
- 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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:15 p.m.