Triple
T29102468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin Derby |
E736672
|
entity |
| Predicate | hasHomeGroundForKeyClub |
P164581
|
FINISHED |
| Object | Tallaght Stadium |
—
|
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: Tallaght Stadium | Statement: [Dublin Derby, hasHomeGroundForKeyClub, Tallaght Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeGroundForKeyClub Context triple: [Dublin Derby, hasHomeGroundForKeyClub, Tallaght Stadium]
-
A.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
B.
hasCountryClubLocation
Indicates that a country club is located at, or associated with, a specific geographic place or address.
-
C.
hasKeyClub
Indicates that an entity is associated with or belongs to a Key Club organization or group.
-
D.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
E.
homeGroundOfAssociatedClub
chosen
Indicates that a particular venue or ground serves as the designated home location for an associated sports club.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 28, 2026, 11:13 a.m.