Triple
T21092082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VR&E |
E519660
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | VR&E |
—
|
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: VR&E | Statement: [VR&E, hasAbbreviation, VR&E]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VR&E Context triple: [VR&E, hasAbbreviation, VR&E]
-
A.
VR&E
chosen
VR&E is a U.S. Department of Veterans Affairs program that helps eligible veterans and service members with service-connected disabilities prepare for, find, and maintain suitable employment or achieve independent living.
-
B.
VRT
VRT is Belgium’s public-service broadcaster for the Flemish Community, providing television, radio, and online media.
-
C.
VRG
VRG is the ICAO airline designator for Varig, the former Brazilian flag carrier and one of Latin America's historically significant airlines.
-
D.
VRU
VRU is the commonly used Ukrainian abbreviation for the Verkhovna Rada, the unicameral parliament and supreme legislative body of Ukraine.
-
E.
VES
VES is an abbreviation for the Virtual Execution System, a runtime environment designed to execute managed code in a platform-independent manner.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:51 p.m.