Triple
T9558213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CH-FR |
E230597
|
entity |
| Predicate | relatesToISO3166-1Code |
P75262
|
FINISHED |
| Object | CH |
E806475
|
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: CH | Statement: [CH-FR, relatesToISO3166-1Code, CH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CH Context triple: [CH-FR, relatesToISO3166-1Code, CH]
-
A.
CH
CH is the post-nominal abbreviation for Companion of Honour, a prestigious British award recognizing outstanding achievements in fields such as the arts, literature, music, science, politics, industry, or religion.
-
B.
CH
CH is the common abbreviation for Christ’s Hospital, a historic English independent boarding school founded in the 16th century and known for its distinctive bluecoat uniform and charitable educational mission.
-
C.
CH
chosen
CH is the ISO 3166-1 alpha-2 country code for Switzerland.
-
D.
CH
CH is the postcode area covering Chester and its surrounding region in northwest England.
-
E.
CH
CH is the standard abbreviation used by the United States Army to designate members of its Chaplain Corps.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99487b4c819086e02e29e37b593f |
completed | April 1, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d17900ae2c819087a83f6c74a59afc |
completed | April 4, 2026, 8:48 p.m. |
Created at: March 30, 2026, 8:03 p.m.