Triple
T16026129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDV |
E388721
|
entity |
| Predicate | notableModel |
P1503
|
FINISHED |
| Object | LDV Pilot |
E388721
|
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: LDV Pilot | Statement: [LDV, notableModel, LDV Pilot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LDV Pilot Context triple: [LDV, notableModel, LDV Pilot]
-
A.
LDV
chosen
LDV was a British commercial vehicle manufacturer best known for producing vans and minibuses, particularly for business and fleet use.
-
B.
LEVD
LEVD is the ICAO airport code assigned to Valladolid Airport in Spain.
-
C.
Man Vehicle Laboratory
Man Vehicle Laboratory is an MIT research lab focused on human factors, human–machine interaction, and human performance in aerospace and other complex vehicle systems.
-
D.
LSV
LSV is the IATA airport code for the military airfield serving Nellis Air Force Base near Las Vegas, Nevada.
-
E.
LCV
LCV (Light Commercial Vehicle) refers to a class of small to medium-sized commercial vans and trucks designed primarily for goods transport and business use.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1832790548190a74045d554e13328 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf31c8d8819096c562ba1453f3c0 |
completed | May 10, 2026, 12:20 a.m. |
Created at: April 10, 2026, 4:56 a.m.