Triple
T23782000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullaghan |
E587839
|
entity |
| Predicate | onlySeasideSettlementOf |
P153912
|
FINISHED |
| Object | County Leitrim |
—
|
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: County Leitrim | Statement: [Tullaghan, onlySeasideSettlementOf, County Leitrim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlySeasideSettlementOf Context triple: [Tullaghan, onlySeasideSettlementOf, County Leitrim]
-
A.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
B.
isOneOfOlderSettlementsIn
Indicates that an entity is among the earlier or historically older settlements located within a specified area or region.
-
C.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
-
D.
typicalSettlement
Indicates that the subject is a common or characteristic type of settlement typically found in the context of the object.
-
E.
sisterSettlement
Indicates that two settlements are formally paired or twinned, typically to promote cultural, social, or economic exchange.
- F. None of above. chosen
Provenance (4 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62d7c608190b5fd0cf35f5faf42 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:16 p.m.