Triple
T486935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westerkerk, Amsterdam |
E9897
|
entity |
| Predicate | hasCoordinate |
P10142
|
FINISHED |
| Object | 52.3747° N, 4.8836° 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: 52.3747° N, 4.8836° E | Statement: [Westerkerk, Amsterdam, hasCoordinate, 52.3747° N, 4.8836° E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoordinate Context triple: [Westerkerk, Amsterdam, hasCoordinate, 52.3747° N, 4.8836° E]
-
A.
hasCoordinates
chosen
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
C.
hasCoordinateSingularity
Indicates that something possesses a point or region where its coordinate description becomes undefined or degenerate, even if the underlying object or space may remain well-behaved.
-
D.
hasSummitCoordinates
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
E.
coordinatesWith
Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0de66308190a18503a482881cfc |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf63fbc819090ea6ca11f39116a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.