Triple
T16484149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compagnie Générale d’Electricité |
E400394
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | CGE |
E400394
|
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: CGE | Statement: [Compagnie Générale d’Electricité, abbreviation, CGE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CGE Context triple: [Compagnie Générale d’Electricité, abbreviation, CGE]
-
A.
CGE
CGE is a French association that brings together the country’s leading grandes écoles, representing elite higher education and research institutions.
-
B.
CGE
CGE is the national governing body responsible for selecting and managing England’s team for the Commonwealth Games and related events.
-
C.
CGE
chosen
CGE is the abbreviation for Compagnie Générale d’Electricité, a former major French industrial and telecommunications conglomerate.
-
D.
GEC
GEC is the ICAO airline designator used by Lufthansa Cargo, the air freight division of Lufthansa.
-
E.
GEG
GEG is the three-letter IATA airport code for Spokane International Airport in Spokane, Washington.
- 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_69d883813098819084f5409539723b59 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e05bf448190947b9da15fd29d0a |
completed | April 18, 2026, 7:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a005820790c819088d953eeea09328d |
completed | May 10, 2026, 10:04 a.m. |
Created at: April 10, 2026, 5:13 a.m.