Triple
T9991901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Medium STOL Transport program |
E196904
|
entity |
| Predicate | relatedRequirement |
P91460
|
FINISHED |
| Object | replacement or supplement for existing tactical transports such as the C-130 Hercules |
—
|
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 or supplement for existing tactical transports such as the C-130 Hercules | Statement: [Advanced Medium STOL Transport program, relatedRequirement, replacement or supplement for existing tactical transports such as the C-130 Hercules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRequirement Context triple: [Advanced Medium STOL Transport program, relatedRequirement, replacement or supplement for existing tactical transports such as the C-130 Hercules]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
basedOnRequirementOf
Indicates that something is established, created, or determined according to a specified requirement or set of requirements.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
E.
establishedRequirement
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
- 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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcb95842c8190b8cdce9584f19840 |
completed | April 2, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:50 p.m.