Triple
T31048514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inis Meáin |
E791192
|
entity |
| Predicate | relativeToOtherIslands |
P56550
|
FINISHED |
| Object | between Inis Mór and Inis Oírr |
—
|
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: between Inis Mór and Inis Oírr | Statement: [Inis Meáin, relativeToOtherIslands, between Inis Mór and Inis Oírr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToOtherIslands Context triple: [Inis Meáin, relativeToOtherIslands, between Inis Mór and Inis Oírr]
-
A.
neighboringIsland
Indicates that one island is geographically adjacent to or very close to another island, typically separated only by a narrow body of water.
-
B.
associatedIsland
Indicates that one entity is related to or connected with a particular island in some relevant way.
-
C.
accessFromOtherIslands
Indicates that something can be reached or utilized from locations situated on other islands.
-
D.
betweenIsland
chosen
Indicates a spatial relationship where something is located in the area separating two or more islands.
-
E.
hasNearbyMainIsland
Indicates that one entity has a main island located in close geographic proximity to it.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9 p.m.