Triple
T21678217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Districts cricket team |
E535028
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | CD |
—
|
NE NERFINISHED |
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: CD | Statement: [Central Districts cricket team, shortName, CD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CD Context triple: [Central Districts cricket team, shortName, CD]
-
A.
CD
A CD is a digital optical disc format commonly used for storing and playing back audio recordings and other data.
-
B.
CD
CD is the abbreviated name for the Consular Directorate, a governmental body responsible for managing consular affairs and services.
-
C.
CD
CD is the commonly used abbreviation for the Conference on Disarmament, the primary multilateral disarmament negotiating forum of the international community.
-
D.
CD
CD is a Canadian honorific suffix indicating that the holder has been awarded the Canadian Forces Decoration for long and meritorious military service.
-
E.
CD
chosen
CD is the common abbreviation for the Chunichi Dragons, a professional baseball team based in Nagoya, Japan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef8a11088081908911af2629f54c1c |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 16, 2026, 6:43 p.m.