Triple
T25947391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Нос Емине |
E653875
|
entity |
| Predicate | approxCoordinates |
P10760
|
FINISHED |
| Object | 42.7°N 27.9°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: 42.7°N 27.9°E | Statement: [Нос Емине, approxCoordinates, 42.7°N 27.9°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxCoordinates Context triple: [Нос Емине, approxCoordinates, 42.7°N 27.9°E]
-
A.
hasApproximateCoordinates
chosen
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
B.
coordinatesIn
Indicates that one entity specifies the spatial coordinates or position of another entity within a given reference frame or system.
-
C.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 22, 2026, 8:43 a.m.