Triple
T16512788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verband der Automobilindustrie |
E401103
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | VDA |
E927861
|
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: VDA | Statement: [Verband der Automobilindustrie, shortName, VDA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VDA Context triple: [Verband der Automobilindustrie, shortName, VDA]
-
A.
VDA
chosen
VDA is the IATA airport code for Ovda Airport, a former joint military-civilian airfield in southern Israel that has handled international charter and low-cost flights.
-
B.
VAND
VAND is the ICAO airport code assigned to Shri Guru Gobind Singh Ji Airport in India.
-
C.
VDV
VDV is the elite airborne branch of Russia’s armed forces, known for rapid-deployment paratrooper and air-assault operations.
-
D.
VAN
VAN is the standard abbreviation used for the Vancouver Canadians, a Minor League Baseball team based in Vancouver, British Columbia.
-
E.
VDP
VDP is a networking protocol used to automatically discover and configure virtual devices or ports in virtualized environments.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e78d4848190a55de9902115b1b2 |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0060827d988190b2c0c075a49dfde8 |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:14 a.m.