Triple
T4438294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UAE President's Cup |
E95706
|
entity |
| Predicate | matchOutcomeFormat |
P46686
|
FINISHED |
| Object | single-leg ties |
—
|
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-leg ties | Statement: [UAE President's Cup, matchOutcomeFormat, single-leg ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchOutcomeFormat Context triple: [UAE President's Cup, matchOutcomeFormat, single-leg ties]
-
A.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
B.
hasMatchFormat
chosen
Indicates that something (such as a game, event, or competition) is conducted according to a specified match format or structure.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
competitionFormat
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
E.
gameOutcome
Indicates the result or final status of a game, such as which side won, lost, or if it ended in a draw.
- 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.