Triple
T18570651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Asia Cup |
E453863
|
entity |
| Predicate | superFourFormat |
P132613
|
FINISHED |
| Object | single round-robin |
—
|
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 round-robin | Statement: [2022 Asia Cup, superFourFormat, single round-robin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superFourFormat Context triple: [2022 Asia Cup, superFourFormat, single round-robin]
-
A.
firstFourFormat
Indicates that the first four characters of a value follow or match a specified format or pattern.
-
B.
semiFinalFormat
Indicates the structure or rules used to organize and play the semifinal stage of a competition or tournament.
-
C.
typicalFinalFormat
Indicates that something represents the usual or standard structure or arrangement in which an item, document, or data is ultimately presented or delivered.
-
D.
fourthSingle
Indicates that an entity is the fourth individual item or occurrence in a sequence, considered on its own rather than as part of a group.
-
E.
overseesFormat
Indicates that one entity is responsible for supervising, managing, or controlling the format or formatting standards of 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b01331c8190bec3aba40358a843 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.