Triple
T26074325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portmarnock Golf Club |
E657637
|
entity |
| Predicate | hostedEventLevel |
P81626
|
FINISHED |
| Object | international championships |
—
|
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: international championships | Statement: [Portmarnock Golf Club, hostedEventLevel, international championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedEventLevel Context triple: [Portmarnock Golf Club, hostedEventLevel, international championships]
-
A.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
hostedEventAreaFor
Indicates that a particular area or location served as the venue or physical space where an event was hosted or took place.
-
C.
leagueLevelHosted
Indicates the competitive tier or division level at which an event, match, or competition is hosted within a league structure.
-
D.
eventLevel
chosen
Indicates the intensity, magnitude, or severity associated with an event within a defined scale or hierarchy.
-
E.
affiliationLevelHosted
Indicates the degree or status of an entity’s affiliation in the context of being hosted by another entity.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 7:32 p.m.