Triple
T19845025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seonjeongneung |
E476836
|
entity |
| Predicate | cityCoordinateSystem |
P1573
|
FINISHED |
| Object | approximately 37.508°N 127.044°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: approximately 37.508°N 127.044°E | Statement: [Seonjeongneung, cityCoordinateSystem, approximately 37.508°N 127.044°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityCoordinateSystem Context triple: [Seonjeongneung, cityCoordinateSystem, approximately 37.508°N 127.044°E]
-
A.
coordinatesUseOf
Indicates that one entity organizes and manages the collaborative use or deployment of another entity’s resources, actions, or functions.
-
B.
coordinateLocation
chosen
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
coordinatesDoctrineIn
Indicates that one entity organizes and aligns doctrinal matters or policies within a specified context, domain, or location.
-
D.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
E.
mapSystem
Indicates a relationship where one system is associated with or represented by a specific map or mapping framework.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658091c608190b4eb9bcedd88e147 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.