Triple
T34220595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Curragh racecourse |
E877911
|
entity |
| Predicate | hasTrainingGrounds |
P2424
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [The Curragh racecourse, hasTrainingGrounds, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingGrounds Context triple: [The Curragh racecourse, hasTrainingGrounds, yes]
-
A.
trainingGroundFor
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
-
B.
trainingGround
chosen
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
C.
servesAsTrainingBaseFor
Indicates that one entity functions as a location or facility where another entity receives training or practical preparation.
-
D.
hasTrainingBaseIn
Indicates that an entity maintains or operates a training base located in a specified place.
-
E.
hasNearbyMilitaryTrainingArea
Indicates that an entity is located close to a designated area used for military training activities.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: May 1, 2026, 1:55 a.m.