Triple
T35427727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achill Sound |
E1023964
|
entity |
| Predicate | isMainGatewaySettlementFor |
P97758
|
FINISHED |
| Object | Achill Island |
—
|
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: Achill Island | Statement: [Achill Sound, isMainGatewaySettlementFor, Achill Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainGatewaySettlementFor Context triple: [Achill Sound, isMainGatewaySettlementFor, Achill Island]
-
A.
isKeySettlementOn
chosen
Indicates that a settlement serves as a primary or strategically important location situated on a specified route, feature, or area.
-
B.
isInSettlementType
Indicates that one entity is located within or classified as belonging to a particular type of settlement (such as a city, town, or village).
-
C.
hasSettlementRole
Indicates that an entity holds or is assigned a specific functional role or status within a settlement.
-
D.
isSettlement
Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
-
E.
supersededAsMainGatewayBy
Indicates that one gateway previously serving as the primary or main access point has been replaced in that role by another gateway.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.