Triple
T7977266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Forces Decoration |
E185476
|
entity |
| Predicate | hasPostNominalLetters |
P1804
|
FINISHED |
| Object | CD |
E413728
|
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: CD | Statement: [Canadian Forces Decoration, hasPostNominalLetters, CD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CD Context triple: [Canadian Forces Decoration, hasPostNominalLetters, CD]
-
A.
CD
chosen
CD is a Canadian honorific suffix indicating that the holder has been awarded the Canadian Forces Decoration for long and meritorious military service.
-
B.
CD
CD is the common abbreviation for the Chunichi Dragons, a professional baseball team based in Nagoya, Japan.
-
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
A CD is a digital optical disc format commonly used for storing and playing back audio recordings and other data.
-
E.
Cd
Cd is an abbreviation used for a series of British government Command Papers published in the early 20th century.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca829851908190b4e03829353ee7c3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bf716508190b4245bd5d89ae8c4 |
completed | March 31, 2026, 3:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63b72c508190b0ad8acf975c1527 |
completed | April 1, 2026, 12:15 a.m. |
Created at: March 30, 2026, 5:14 p.m.