Triple
T16913204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LAV-25 family |
E410252
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | LAV-AD |
E408948
|
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: LAV-AD | Statement: [LAV-25 family, hasVariant, LAV-AD]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LAV-AD Context triple: [LAV-25 family, hasVariant, LAV-AD]
-
A.
LAV-AD
chosen
The LAV-AD is an air-defense variant of the U.S. Marine Corps’ Light Armored Vehicle family, equipped with anti-aircraft guns and missile systems to engage low-flying aircraft and helicopters.
-
B.
LAV-R
The LAV-R is a U.S. Marine Corps light armored vehicle variant configured as a recovery and maintenance platform to support other light armored vehicles in the field.
-
C.
LAV-L
The LAV-L is a light armored vehicle variant used by the U.S. Marine Corps primarily as a logistics and support platform within light armored reconnaissance units.
-
D.
LAV-AT
The LAV-AT is a U.S. Marine Corps light armored vehicle variant equipped with anti-tank guided missile systems designed to engage and destroy enemy armored threats.
-
E.
LAV-C2
The LAV-C2 is a command and control variant of the U.S. Marine Corps’ Light Armored Vehicle designed to provide mobile battlefield communications and coordination capabilities.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3ca3e6b9481909fbaeb0bddd7e3b2 |
completed | April 18, 2026, 6:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d458902481908f79cd5a9f72f7fd |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:30 a.m.