Triple
T4438304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UAE President's Cup |
E95706
|
entity |
| Predicate | tournamentSystem |
P2673
|
FINISHED |
| Object | single-elimination |
—
|
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: single-elimination | Statement: [UAE President's Cup, tournamentSystem, single-elimination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentSystem Context triple: [UAE President's Cup, tournamentSystem, single-elimination]
-
A.
matingSystem
Indicates the type or pattern of reproductive pairing or mating relationships that typically occurs within a species or population.
-
B.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
-
C.
rivalryTournament
Indicates a competitive relationship where entities repeatedly oppose each other in a structured tournament setting, emphasizing ongoing rivalry.
-
D.
managedTournament
Indicates that one entity was responsible for organizing, overseeing, or administering a particular tournament.
-
E.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558c75948190875a5fb10eac0597 |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.