Triple
T4319411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT40 cased telescoped weapon system |
E96474
|
entity |
| Predicate | designedForEra |
P36703
|
FINISHED |
| Object | contemporary armored warfare |
—
|
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: contemporary armored warfare | Statement: [CT40 cased telescoped weapon system, designedForEra, contemporary armored warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForEra Context triple: [CT40 cased telescoped weapon system, designedForEra, contemporary armored warfare]
-
A.
appliesToEra
chosen
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
B.
partOfEra
Indicates that one entity exists as a temporal segment or component within the duration or scope of a larger historical era.
-
C.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
D.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
E.
eraOfObsolescence
Indicates the time period during which something becomes outdated, no longer useful, or superseded by newer alternatives.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35112ec008190958487f501481887 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.