Triple
T1778464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pizarro infantry fighting vehicle |
E39233
|
entity |
| Predicate | introducedAsReplacementFor |
P6280
|
FINISHED |
| Object | older Spanish tracked APCs |
—
|
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: older Spanish tracked APCs | Statement: [Pizarro infantry fighting vehicle, introducedAsReplacementFor, older Spanish tracked APCs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsReplacementFor Context triple: [Pizarro infantry fighting vehicle, introducedAsReplacementFor, older Spanish tracked APCs]
-
A.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
usedInsteadOf
chosen
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
D.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
E.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.