Triple
T32752698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaelic Athletic Association |
E837539
|
entity |
| Predicate | notableVenueOwned |
P73096
|
FINISHED |
| Object | Croke Park |
E253336
|
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: Croke Park | Statement: [Gaelic Athletic Association, notableVenueOwned, Croke Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVenueOwned Context triple: [Gaelic Athletic Association, notableVenueOwned, Croke Park]
-
A.
notableVenueFor
Indicates that a venue is especially recognized or significant for hosting, presenting, or being associated with a particular entity or activity.
-
B.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
C.
notableRecordingVenueFor
Indicates that a venue is particularly recognized or distinguished as the place where a specific recording was made.
-
D.
venueOwner
chosen
Indicates that one entity is the owner or proprietor responsible for a particular venue or event location.
-
E.
hasVenueProperty
Indicates that a venue possesses or is characterized by a specific property or attribute.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34bce7699081908c97052dbe7449cd |
completed | June 19, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.