Triple
T18185477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bolívar venezolano |
E435400
|
entity |
| Predicate | previousISO4217Code |
P11592
|
FINISHED |
| Object | VEF |
—
|
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: VEF | Statement: [bolívar venezolano, previousISO4217Code, VEF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VEF Context triple: [bolívar venezolano, previousISO4217Code, VEF]
-
A.
VEF
chosen
VEF was the ISO 4217 currency code for the Venezuelan bolívar used before its redenomination to the bolívar soberano.
-
B.
VE
VE is the Italian vehicle registration code assigned to the Metropolitan City of Venice.
-
C.
VE
VE is the two-letter ISO 3166-1 alpha-2 country code assigned to Venezuela for international standardization and identification purposes.
-
D.
VFA
VFA is the commonly used abbreviation for the Victorian Football Association, a historic Australian rules football competition based in the state of Victoria.
-
E.
VELO
VELO is the high-precision vertex detector of the LHCb experiment at CERN, designed to measure particle trajectories very close to the proton–proton collision point.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffdccd881908da772db78b9d081 |
completed | April 19, 2026, 2 p.m. |
Created at: April 10, 2026, 10:31 a.m.