Triple
T18254152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental AG |
E437177
|
entity |
| Predicate | hasTickerSymbol |
P1447
|
FINISHED |
| Object | CON |
—
|
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: CON | Statement: [Continental AG, hasTickerSymbol, CON]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CON Context triple: [Continental AG, hasTickerSymbol, CON]
-
A.
CON
chosen
CON is the stock ticker symbol for Continental AG, a major German automotive parts manufacturer and tire producer.
-
B.
CON
CON is a Nigerian national honor post-nominal indicating a recipient of the Commander of the Order of the Niger.
-
C.
CONT
CONT is the European Parliament’s Committee on Budgetary Control, responsible for overseeing the implementation and proper use of the European Union budget.
-
D.
Con
Con is a common diminutive or nickname for the given name Conrad.
-
E.
CONS
CONS is the National Olympic Committee responsible for organizing and overseeing San Marino’s participation in the Olympic Games and other international sporting events.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4fd82f81c81909ad4455954bd8caa |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 10:33 a.m.