Triple
T5210122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Counsel |
E117610
|
entity |
| Predicate | honorificSuffix |
P341
|
FINISHED |
| Object | QC |
E273606
|
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: QC | Statement: [Queen's Counsel, honorificSuffix, QC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: QC Context triple: [Queen's Counsel, honorificSuffix, QC]
-
A.
QC
chosen
QC (Queen's Counsel) is a prestigious rank awarded to senior barristers in some Commonwealth legal systems, recognizing their excellence and leadership in advocacy.
-
B.
QC
QC is a common abbreviation for Quezon City, a major urban center and former capital located in Metro Manila, Philippines.
-
C.
The QC
The QC is a popular nickname for Charlotte, North Carolina, reflecting its identity as a major financial and cultural hub in the southeastern United States.
-
D.
CA-QC
CA-QC is the ISO 3166-2 subdivision code that uniquely identifies the Canadian province of Quebec.
-
E.
QA
QA is the station code for Quincy Adams, a Massachusetts Bay Transportation Authority (MBTA) rapid transit station on Boston’s Red Line.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a703e388190845dedd17252ddde |
completed | March 20, 2026, 4:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bef7ffab8c81908e17e085727304b6 |
completed | March 21, 2026, 7:56 p.m. |
Created at: March 20, 2026, 1:47 p.m.