Triple
T18506696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verizon Communications Inc. |
E452214
|
entity |
| Predicate | tickerSymbol |
P1447
|
FINISHED |
| Object | VZ |
—
|
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: VZ | Statement: [Verizon Communications Inc., tickerSymbol, VZ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VZ Context triple: [Verizon Communications Inc., tickerSymbol, VZ]
-
A.
VZ
chosen
VZ is the stock ticker symbol for Verizon Communications Inc., a major U.S.-based telecommunications company providing wireless, internet, and related services.
-
B.
VŽ
VŽ is the vehicle registration code used for the town of Ludbreg in Croatia.
-
C.
VZIO
VZIO is the stock ticker symbol for Vizio Holding Corp., an American company known for manufacturing affordable smart TVs and related consumer electronics.
-
D.
VZL
VZL is the station code for Vijzelgracht metro station on Amsterdam’s North–South metro line.
-
E.
ZVO
ZVO is the Russian abbreviation for the Western Military District, one of Russia’s main strategic military commands responsible for forces in the country’s western regions.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334266708190b59aca3a2218c095 |
completed | April 19, 2026, 7:55 p.m. |
Created at: April 10, 2026, 11:36 a.m.