Triple
T29780967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XM2001 Crusader |
E756111
|
entity |
| Predicate | intendedMobility |
P186375
|
FINISHED |
| Object | tracked armored vehicle |
—
|
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: tracked armored vehicle | Statement: [XM2001 Crusader, intendedMobility, tracked armored vehicle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMobility Context triple: [XM2001 Crusader, intendedMobility, tracked armored vehicle]
-
A.
supportsMobilityBetween
Indicates that one entity enables, facilitates, or allows movement or travel between two or more other entities or locations.
-
B.
hasMobilityConcept
Indicates a relationship where an entity is associated with, or characterized by, a specific concept or model of mobility (e.g., movement, transportation, or locomotion).
-
C.
mobilityRule
Indicates a rule or constraint governing how an entity is allowed or able to move or change location within a given context.
-
D.
mobilityMethod
Indicates the means or method by which an entity moves or is transported from one place to another.
-
E.
intendedNetwork
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
- F. None of above. chosen
Provenance (4 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 29, 2026, 5:05 p.m.