Triple
T37435751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arranmore Island |
E930258
|
entity |
| Predicate | nearestMainlandSettlement |
P64847
|
FINISHED |
| Object | Burtonport |
—
|
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: Burtonport | Statement: [Arranmore Island, nearestMainlandSettlement, Burtonport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMainlandSettlement Context triple: [Arranmore Island, nearestMainlandSettlement, Burtonport]
-
A.
nearestInlandCity
Indicates that one city is the closest inland (non-coastal) city to another specified location.
-
B.
nearestMainlandPoint
chosen
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
C.
nearestCoastalTown
Indicates that one town is the closest coastal town geographically relative to a given reference location or town.
-
D.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
E.
nearestCityTo
Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.