Triple
T30078140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterford senior hurling team |
E764380
|
entity |
| Predicate | alternativeGround |
P175260
|
FINISHED |
| Object | Fraher Field |
—
|
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: Fraher Field | Statement: [Waterford senior hurling team, alternativeGround, Fraher Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeGround Context triple: [Waterford senior hurling team, alternativeGround, Fraher Field]
-
A.
alternativeTerminus
Indicates that something serves as another possible endpoint or final destination in place of, or in addition to, a primary terminus.
-
B.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
C.
alternativeRoute
Indicates that there exists a different path or option that can be taken instead of the primary or original route.
-
D.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
E.
alternativeFlag
Indicates that something is marked or designated as an alternative option or variant relative to a primary or default choice.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 29, 2026, 7:02 p.m.