Triple
T28815796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reek Sunday pilgrimage |
E727637
|
entity |
| Predicate | takesPlaceInCounty |
P23957
|
FINISHED |
| Object | County Mayo |
—
|
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 Mayo | Statement: [Reek Sunday pilgrimage, takesPlaceInCounty, County Mayo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPlaceInCounty Context triple: [Reek Sunday pilgrimage, takesPlaceInCounty, County Mayo]
-
A.
inCounty
chosen
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
B.
operatesInCounty
Indicates that an entity conducts its activities or provides its services within the geographic boundaries of a specified county.
-
C.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
D.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
E.
locatedInCountySeatOfCounty
Indicates that one entity is located in the county seat city or town of the specified county.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 6:32 a.m.