Triple
T3943800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulster Cup |
E92095
|
entity |
| Predicate | winnerType |
P52161
|
FINISHED |
| Object | club side |
—
|
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: club side | Statement: [Ulster Cup, winnerType, club side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerType Context triple: [Ulster Cup, winnerType, club side]
-
A.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
B.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
C.
winnerRight
Indicates that the referenced entity is the winner on the right side or right position in a competitive or comparative context.
-
D.
winnerTitle
Indicates the formal title or designation awarded to the entity that wins a particular competition, contest, or event.
-
E.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
- F. None of above. chosen
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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:24 p.m.