Triple

T16741088
Position Surface form Disambiguated ID Type / Status
Subject ASLAV E406834 entity
Predicate hasVariant P455 FINISHED
Object ASLAV-F E1230261 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: ASLAV-F | Statement: [ASLAV, hasVariant, ASLAV-F]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ASLAV-F
Context triple: [ASLAV, hasVariant, ASLAV-F]
  • A. ASLAV-PC chosen
    The ASLAV-PC is an Australian Light Armoured Vehicle variant configured as a personnel carrier, designed to transport infantry with protection and mobility in combat environments.
  • B. ASLV
    ASLV (Augmented Satellite Launch Vehicle) was an early Indian small-lift launch vehicle developed by ISRO as a technological stepping stone toward more advanced rockets like the PSLV.
  • C. ASLIA
    ASLIA is the professional association representing and supporting sign language interpreters in Australia.
  • D. SLAF
    SLAF is the acronym for the Sri Lanka Air Force, the aerial warfare branch of Sri Lanka’s armed forces.
  • E. ASV
    ASV is a 1901 English Bible translation known for its formal, literal rendering of the original Hebrew and Greek texts.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e39c3e87348190acaf7c40e8f8b566 completed April 18, 2026, 2:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00aaf1853c819084d636afe8f3cb2e completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:20 a.m.