Triple
T6197207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada national cricket team |
E138537
|
entity |
| Predicate | hasPlayerCategory |
P29723
|
FINISHED |
| Object | Canada One Day International cricketers |
—
|
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: Canada One Day International cricketers | Statement: [Canada national cricket team, hasPlayerCategory, Canada One Day International cricketers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlayerCategory Context triple: [Canada national cricket team, hasPlayerCategory, Canada One Day International cricketers]
-
A.
hasPlayer
chosen
Indicates that an entity (such as a team, game, or roster) includes or is associated with a specific player.
-
B.
hasCompetitionCategory
Indicates that an entity is associated with a specific category or division within a competition.
-
C.
hasStudentCategory
Indicates that an entity is classified under a specific category or type of student.
-
D.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062508f5c8190a00291708a9a7de9 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.