Triple
T32730180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger 3 |
E836926
|
entity |
| Predicate | hasUpgradeProgramName |
P89116
|
FINISHED |
| Object | Challenger 2 Life Extension Programme |
—
|
NE NERFINISHED |
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: Challenger 2 Life Extension Programme | Statement: [Challenger 3, hasUpgradeProgramName, Challenger 2 Life Extension Programme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpgradeProgramName Context triple: [Challenger 3, hasUpgradeProgramName, Challenger 2 Life Extension Programme]
-
A.
hasUpgrade
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
B.
upgradeProgrammeName
chosen
Indicates the name assigned to a specific upgrade programme associated with an entity.
-
C.
hasUpgradeProject
Indicates that an entity is associated with a project whose purpose is to improve, enhance, or modernize that entity.
-
D.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
-
E.
associatedWithUpgradePrograms
Indicates a relationship where an entity is linked to, participates in, or is covered by one or more upgrade programs.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:11 a.m.