Triple
T5581881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC World Test Championship |
E146658
|
entity |
| Predicate | usesPointsTable |
P53177
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ICC World Test Championship, usesPointsTable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPointsTable Context triple: [ICC World Test Championship, usesPointsTable, true]
-
A.
usesPointsForDraw
Indicates that an entity relies on or applies a points-based system to determine or execute a draw (such as a lottery, selection, or outcome).
-
B.
usesPointsForLoss
Indicates that a system or rule assigns or deducts points to represent or account for a loss.
-
C.
pointsEarnedFrom
Indicates the number of points that an entity has received as a result of another specified source, action, or event.
-
D.
usedInTournamentTables
chosen
Indicates that something (such as a rule, format, or data structure) is employed within the context of tournament tables.
-
E.
tryPoints
Indicates an attempt by one entity to score or gain points, typically through some action or effort directed toward achieving those points.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208147a48190b2cdb42b9c9814a3 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.