Triple
T16741091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASLAV |
E406834
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | ASLAV-A |
E406834
|
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-A | Statement: [ASLAV, hasVariant, ASLAV-A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ASLAV-A Context triple: [ASLAV, hasVariant, ASLAV-A]
-
A.
ASLAV-PC
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.
ASLAV armoured vehicle
chosen
The ASLAV armoured vehicle is an Australian variant of the LAV-25 family, used as a highly mobile, amphibious, wheeled armoured fighting vehicle for reconnaissance and combat support roles.
-
C.
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.
-
D.
ASV
ASV is a 1901 English Bible translation known for its formal, literal rendering of the original Hebrew and Greek texts.
-
E.
ASLIA
ASLIA is the professional association representing and supporting sign language interpreters in Australia.
- 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_6a00c2993f4c8190aecf29a4bcbf7b6a |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:20 a.m.