Triple
T36271095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland national cricket team |
E892675
|
entity |
| Predicate | firstODIMatchOpponent |
P8304
|
FINISHED |
| Object | Australia |
E876
|
NE 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: Australia | Statement: [Scotland national cricket team, firstODIMatchOpponent, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstODIMatchOpponent Context triple: [Scotland national cricket team, firstODIMatchOpponent, Australia]
-
A.
firstODIMatchTeams
Indicates that the related entities are the teams that played in the first One Day International (ODI) match between them.
-
B.
firstRoundOpponent
Indicates that one entity is the opponent another entity faces in the first round of a competition or tournament.
-
C.
firstODIMatchYear
Indicates the year in which an entity (typically a player or team) participated in its first One Day International (ODI) cricket match.
-
D.
firstGameOpponent
chosen
Indicates that one entity is the opponent faced by another entity in its first game or match.
-
E.
highestODIScoreOpponent
Indicates the opposing team or player against whom an entity has achieved its highest individual ODI (One Day International) score.
- F. None of above.
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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a396e0fb8908190a15671549c7e0c73 |
completed | June 22, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.