Triple
T28815900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National pilgrimage on Reek Sunday |
E727639
|
entity |
| Predicate | associatedLocalName |
P97559
|
FINISHED |
| Object | The Reek |
E727626
|
NE 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 Reek | Statement: [National pilgrimage on Reek Sunday, associatedLocalName, The Reek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLocalName Context triple: [National pilgrimage on Reek Sunday, associatedLocalName, The Reek]
-
A.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
B.
notableLocalName
chosen
Indicates that an entity is known by a notable or commonly used local name within a specific region or community.
-
C.
associatedBaseName
Indicates that one entity is linked to or derived from another entity’s base or canonical name.
-
D.
associatedNewName
Indicates that an entity is linked to or identified by a newly assigned name or label.
-
E.
representedLocallyBy
Indicates that an entity is expressed, implemented, or instantiated in a specific local form or representation by another entity.
- F. None of above.
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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d3edf134819095a8da1cd7781edb |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
Created at: April 28, 2026, 6:32 a.m.