Triple
T18570653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2022 Asia Cup |
E453863
|
entity |
| Predicate | matchesPlayedAs |
P132614
|
FINISHED |
| Object | night matches |
—
|
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: night matches | Statement: [2022 Asia Cup, matchesPlayedAs, night matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchesPlayedAs Context triple: [2022 Asia Cup, matchesPlayedAs, night matches]
-
A.
matchesPlayedIn
Indicates that a particular match was played in a specified location, event, or competition context.
-
B.
totalMatchesPlayed
Indicates the total number of matches that have been played by the referenced entity or between the related entities.
-
C.
qualificationMatchesPlayed
Indicates that the number of qualification matches associated with an entity has been played or completed.
-
D.
leagueMatchesPlayed
Indicates the number of matches an entity has participated in within a specific league competition.
-
E.
sportNumberOfAppearances
Indicates the total number of times an entity has participated in or appeared in a particular sport or sporting event.
- 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.