Triple

T23536286
Position Surface form Disambiguated ID Type / Status
Subject Laval Rocket E576708 entity
Predicate abbreviation P43 FINISHED
Object LAV 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: LAV | Statement: [Laval Rocket, abbreviation, LAV]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LAV
Context triple: [Laval Rocket, abbreviation, LAV]
  • A. 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.
  • B. LAV-M
    The LAV-M is a mortar-armed variant of the U.S. Marine Corps’ Light Armored Vehicle family, designed to provide mobile, armored indirect fire support to reconnaissance and infantry units.
  • C. LVA
    LVA is the three-letter ISO 3166-1 alpha-3 country code for Latvia.
  • D. LAV (leisure activity vehicle) chosen
    The LAV (leisure activity vehicle) is a compact, van-based multi-purpose vehicle designed to combine passenger comfort with flexible cargo space for everyday and recreational use.
  • E. LAV-AD
    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.
  • 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ae1738bc81909a7b761ddbaa1883 completed April 29, 2026, 7:07 a.m.
Created at: April 17, 2026, 6:10 p.m.