Triple
T3330367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilkenau |
E70017
|
entity |
| Predicate | hasCoordinateLocationAsOlkusz |
P1573
|
FINISHED |
| Object | 50.281°N 19.565°E |
—
|
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: 50.281°N 19.565°E | Statement: [Ilkenau, hasCoordinateLocationAsOlkusz, 50.281°N 19.565°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinateLocationAsOlkusz Context triple: [Ilkenau, hasCoordinateLocationAsOlkusz, 50.281°N 19.565°E]
-
A.
hasCoordinates
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
coordinateLocation
chosen
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
hasCoordinateRole
Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.