Triple
T675913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric |
E13076
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | GE |
E13076
|
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: GE | Statement: [General Electric, tickerSymbol, GE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GE Context triple: [General Electric, tickerSymbol, GE]
-
A.
GE
GE is the ISO 3166-1 alpha-2 country code for Georgia, a nation at the crossroads of Eastern Europe and Western Asia.
-
B.
General Electric
chosen
General Electric is a major American multinational conglomerate historically known for its leadership in industrial manufacturing, aviation, power, and healthcare technologies.
-
C.
General Motors
General Motors is a major American multinational automotive manufacturer known for brands such as Chevrolet, GMC, Cadillac, and Buick.
-
D.
Ford
Ford is a common English surname borne by numerous notable individuals, including U.S. President Gerald Ford.
-
E.
LG
LG is the post-nominal abbreviation used by members of the prestigious British chivalric Order of the Garter.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04b2ae881908a5c23453bef8572 |
completed | March 1, 2026, 8:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a5c3a1b6588190b0c9215afb3a9200 |
completed | March 2, 2026, 5:06 p.m. |
Created at: March 1, 2026, 7:36 p.m.