Triple
T36271096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland national cricket team |
E892675
|
entity |
| Predicate | firstT20IMatchOpponent |
P57823
|
FINISHED |
| Object | Ireland |
E5475
|
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: Ireland | Statement: [Scotland national cricket team, firstT20IMatchOpponent, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstT20IMatchOpponent Context triple: [Scotland national cricket team, firstT20IMatchOpponent, Ireland]
-
A.
firstT20IMatchTeams
Indicates that the related entities are the teams that participated in a player's or nation's first Twenty20 International (T20I) cricket match.
-
B.
internationalDebutOpponentT20I
Indicates the opposing team against which a player made their international T20I debut.
-
C.
lastT20iAgainst
Indicates the opponent team a side most recently played against in a Twenty20 International (T20I) match.
-
D.
internationalDebutOpponentODI
Indicates the opposing team against which a player made their One Day International (ODI) debut.
-
E.
t20IDebutOpponent
chosen
Indicates the opponent team against which an entity made its Twenty20 International (T20I) debut.
- 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_6a396e06c19081909434ccbb106bdd5d |
completed | June 22, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.