Triple
T7217001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KC-X program |
E149560
|
entity |
| Predicate | serviceLifeTarget |
P75499
|
FINISHED |
| Object | replacement of aging KC-135 fleet |
—
|
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: replacement of aging KC-135 fleet | Statement: [KC-X program, serviceLifeTarget, replacement of aging KC-135 fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceLifeTarget Context triple: [KC-X program, serviceLifeTarget, replacement of aging KC-135 fleet]
-
A.
serviceAge
Indicates the length of time an entity has been in service or actively performing its role.
-
B.
serviceYears
Indicates the number of years an entity has provided service or been in a particular role, position, or organization.
-
C.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
D.
serviceEra
Indicates the historical period or era during which a service, role, or duty was performed.
-
E.
durationOfUse
Indicates the length of time for which something is used or remains in use.
- F. None of above. chosen
Provenance (4 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e99000dc81908ef4b70729cc00b0 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69c6e889854481908c765ce2107f2d3a |
completed | March 27, 2026, 8:28 p.m. |
Created at: March 27, 2026, 2:53 p.m.