Triple
T33282881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Clochán Liath |
E852094
|
entity |
| Predicate | nearbyAreaServed |
P196011
|
FINISHED |
| Object | The Rosses hinterland |
—
|
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: The Rosses hinterland | Statement: [An Clochán Liath, nearbyAreaServed, The Rosses hinterland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAreaServed Context triple: [An Clochán Liath, nearbyAreaServed, The Rosses hinterland]
-
A.
nearbyCityServed
Indicates that a city is geographically close enough to another city to be considered within its service or support area.
-
B.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
C.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
D.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
-
E.
servesRemoteArea
Indicates that an entity provides services or support to people or locations in geographically remote or hard-to-reach areas.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
| PDg | Predicate description generation | batch_69fe00d8d8248190a63c12aa2c2f7c0c |
completed | May 8, 2026, 3:27 p.m. |
Created at: May 1, 2026, 1:32 a.m.