Triple
T18004007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Next Generation Combat Vehicle |
E430697
|
entity |
| Predicate | replacesOrAugments |
P29646
|
FINISHED |
| Object | legacy armored combat vehicles |
—
|
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: legacy armored combat vehicles | Statement: [Next Generation Combat Vehicle, replacesOrAugments, legacy armored combat vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesOrAugments Context triple: [Next Generation Combat Vehicle, replacesOrAugments, legacy armored combat vehicles]
-
A.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacesInPractice
Indicates that one entity has effectively taken over the role, function, or use of another entity in real-world application or usage.
-
D.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
E.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b3eb1f748190904c8894d22cf85f |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.