Triple
T26005904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elin Pelin Municipality |
E646756
|
entity |
| Predicate | neighboringMajorCity |
P1982
|
FINISHED |
| Object | Sofia |
—
|
NE NERFINISHED |
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: Sofia | Statement: [Elin Pelin Municipality, neighboringMajorCity, Sofia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringMajorCity Context triple: [Elin Pelin Municipality, neighboringMajorCity, Sofia]
-
A.
adjacentMajorCity
Indicates that one major city is geographically next to or directly bordering another major city.
-
B.
nearestMajorCity
chosen
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
C.
largestNearbyCity
Indicates that one city is the largest (by population, area, or another defined metric) among the cities located within a specified nearby region of another place or city.
-
D.
majorCityNearMouth
Indicates that a major city is located close to the mouth (outflow point) of a river.
-
E.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 9 a.m.