Triple
T18569086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Test Team Rankings |
E453830
|
entity |
| Predicate | considersHomeAndAwayResults |
P39328
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ICC Test Team Rankings, considersHomeAndAwayResults, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: considersHomeAndAwayResults Context triple: [ICC Test Team Rankings, considersHomeAndAwayResults, yes]
-
A.
hasHomeAndAwayFormat
chosen
Indicates that a competition, match, or series is structured with both home and away legs or fixtures between the same opponents.
-
B.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
C.
teamOutcome
Indicates the result or consequence experienced by a team as a whole in relation to a specific event, activity, or performance.
-
D.
supportsAwayMatchesOf
Indicates that one entity provides backing, resources, or endorsement specifically for the away matches played by another entity.
-
E.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b0075a08190a5d590d36089ca1e |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.