Triple
T15771050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light Armored Vehicle – Logistics |
E382359
|
entity |
| Predicate | crewCapability |
P56184
|
FINISHED |
| Object | can carry logistics personnel |
—
|
LITERAL 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: can carry logistics personnel | Statement: [Light Armored Vehicle – Logistics, crewCapability, can carry logistics personnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewCapability Context triple: [Light Armored Vehicle – Logistics, crewCapability, can carry logistics personnel]
-
A.
crewLifeSupportCapability
Indicates the ability of a system or vehicle to provide and maintain necessary life support functions for its crew.
-
B.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
C.
crewSystem
Indicates a relationship where a system is specifically designed for, assigned to, or operated by a particular crew.
-
D.
operationalCapability
chosen
Indicates the ability or readiness of an entity to perform a specific function, task, or operation effectively under defined conditions.
-
E.
aircraftCapability
Indicates that an aircraft possesses a particular capability, function, or operational feature.
- F. None of above.
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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051962fe08190a6201dd48196a9ee |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.