Triple
T31816041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAM 2C modernization program |
E812134
|
entity |
| Predicate | typeOfUpgrade |
P23568
|
FINISHED |
| Object | mid‑life upgrade |
—
|
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: mid‑life upgrade | Statement: [TAM 2C modernization program, typeOfUpgrade, mid‑life upgrade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfUpgrade Context triple: [TAM 2C modernization program, typeOfUpgrade, mid‑life upgrade]
-
A.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
B.
upgradeType
chosen
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
C.
partOfUpgrade
Indicates that one entity is included as a component or step within a larger upgrade process or package.
-
D.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
E.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: April 30, 2026, 11:44 p.m.