Triple
T5444399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLI-84 infantry fighting vehicle |
E122211
|
entity |
| Predicate | hasSuspension |
P64117
|
FINISHED |
| Object | torsion bar suspension |
—
|
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: torsion bar suspension | Statement: [MLI-84 infantry fighting vehicle, hasSuspension, torsion bar suspension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuspension Context triple: [MLI-84 infantry fighting vehicle, hasSuspension, torsion bar suspension]
-
A.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
B.
suspendedBy
Indicates that one entity has temporarily halted, removed, or placed another entity in an inactive or pending state, typically as an enforcement or administrative action.
-
C.
suspensionDate
Indicates the date on which an entity’s normal status, operation, or privileges are formally suspended.
-
D.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
E.
suspensionReason
Indicates the reason or cause for which an entity has been suspended from a status, activity, or service.
- 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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd922dc688819092bf33589ebc6d50 |
completed | March 20, 2026, 6:30 p.m. |
Created at: March 20, 2026, 2:07 p.m.