Triple
T21837008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M923A1 |
E539144
|
entity |
| Predicate | hasWinchVariant |
P145508
|
FINISHED |
| Object | M925A1 |
—
|
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: M925A1 | Statement: [M923A1, hasWinchVariant, M925A1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M925A1 Context triple: [M923A1, hasWinchVariant, M925A1]
-
A.
M925
chosen
The M925 is a variant of the U.S. military’s M939 series 5-ton 6x6 tactical cargo truck, designed for heavy transport and off-road logistical support.
-
B.
M923
The M923 is a U.S. military 5-ton 6x6 cargo truck variant used for tactical transport of troops, equipment, and supplies.
-
C.
M928
The M928 is a long-wheelbase cargo variant of the U.S. military M939 series 5-ton 6x6 tactical truck, designed for heavy transport and logistical support.
-
D.
M923A1
The M923A1 is a U.S. military 5-ton 6x6 cargo truck variant designed for tactical transport of troops and equipment across rough terrain.
-
E.
M932
The M932 is a variant of the U.S. military M939-series 5-ton 6x6 tactical truck, configured primarily as a tractor truck for hauling semi-trailers and heavy equipment.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a890208190a902184e60194e1c |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 16, 2026, 6:55 p.m.