Triple
T29102503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenmalure Park |
E736673
|
entity |
| Predicate | successorVenueForTenant |
P178593
|
FINISHED |
| Object | Tolka Park |
—
|
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: Tolka Park | Statement: [Glenmalure Park, successorVenueForTenant, Tolka Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorVenueForTenant Context triple: [Glenmalure Park, successorVenueForTenant, Tolka Park]
-
A.
replacedVenueOfTenant
chosen
Indicates that one venue has taken the place of another as the location occupied or used by a particular tenant.
-
B.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
-
C.
tenantBecame
Indicates that an entity transitioned into the role or status of a tenant at a particular time or under specific conditions.
-
D.
hasSuccessorVenueName
Indicates that one venue is followed or replaced by another venue, whose name is given as the successor venue name.
-
E.
successorFacilityLocation
Indicates that one facility location directly follows or replaces another in a sequence or succession of locations.
- 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_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 28, 2026, 11:13 a.m.