Triple
T32753099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derry GAA |
E837548
|
entity |
| Predicate | secondaryGround |
P197857
|
FINISHED |
| Object | Owenbeg, Dungiven |
—
|
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: Owenbeg, Dungiven | Statement: [Derry GAA, secondaryGround, Owenbeg, Dungiven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryGround Context triple: [Derry GAA, secondaryGround, Owenbeg, Dungiven]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondarySingle
Indicates that an entity serves as a secondary, but singular, counterpart or role in relation to another primary entity.
-
C.
alternativeGround
Indicates that one entity serves as a substitute or backup basis, reason, or justification for another.
-
D.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
-
E.
secondarySurface
Indicates a relationship where one surface functions as a secondary or subordinate surface in relation to a primary or main surface.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: May 1, 2026, 1:12 a.m.