Triple
T1459579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madrid, Cundinamarca |
E31478
|
entity |
| Predicate | geographicCoordinateSystem |
P2054
|
FINISHED |
| Object | near 4.7°N 74.3°W |
—
|
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: near 4.7°N 74.3°W | Statement: [Madrid, Cundinamarca, geographicCoordinateSystem, near 4.7°N 74.3°W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicCoordinateSystem Context triple: [Madrid, Cundinamarca, geographicCoordinateSystem, near 4.7°N 74.3°W]
-
A.
coordinateSystem
chosen
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
B.
geographicCenter
Indicates the location that serves as the central point of a geographic area or region.
-
C.
mapProjection
Indicates the specific method or transformation used to represent locations from the curved surface of the Earth onto a flat map.
-
D.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
E.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59c1c288190be08064f2d351b2b |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.