Triple
T6418860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Namibia national cricket team |
E127894
|
entity |
| Predicate | worldCupDebutYear |
P66342
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Namibia national cricket team, worldCupDebutYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldCupDebutYear Context triple: [Namibia national cricket team, worldCupDebutYear, 2003]
-
A.
WorldCupDebutYear
chosen
Indicates the year in which an entity (typically a team or player) first participated in a World Cup tournament.
-
B.
worldCupAppearanceYear
Indicates the specific year in which an entity participated in a FIFA World Cup tournament.
-
C.
worldCupHostYear
Indicates the year in which a particular country or location served as the host of the FIFA World Cup tournament.
-
D.
wasFirstWorldCupWith
Indicates that the referenced World Cup tournament was the first one to feature or include the specified characteristic, rule, format, or element.
-
E.
internationalTeamDebutYear
Indicates the year in which an entity (typically an athlete) first appeared in competition for an international team.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0690194dc8190b3382bd5f92876b5 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.