Triple
T24947795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midlothian North and Musselburgh |
E624238
|
entity |
| Predicate | borderingCouncilArea |
P154021
|
FINISHED |
| Object | City of Edinburgh |
—
|
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: City of Edinburgh | Statement: [Midlothian North and Musselburgh, borderingCouncilArea, City of Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderingCouncilArea Context triple: [Midlothian North and Musselburgh, borderingCouncilArea, City of Edinburgh]
-
A.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
-
B.
borderingAuthorityOf
chosen
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
C.
countryBorderRelation
Indicates that two countries share a common land or maritime boundary with each other.
-
D.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
E.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:55 a.m.