Triple
T8732294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Tactical Fighter program |
E207285
|
entity |
| Predicate | aircraftRequirement |
P51088
|
FINISHED |
| Object | stealth |
—
|
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: stealth | Statement: [Advanced Tactical Fighter program, aircraftRequirement, stealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRequirement Context triple: [Advanced Tactical Fighter program, aircraftRequirement, stealth]
-
A.
aircraftRoleRequired
Indicates that a specific operational role or function is required of an aircraft within a given context or mission.
-
B.
aircraftCapability
chosen
Indicates that an aircraft possesses a particular capability, function, or operational feature.
-
C.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
-
D.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
E.
aircraftRoleSupported
Indicates that a given role or function is supported or enabled for a particular aircraft.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d2903b08190a5ef29b6d6ca5f1c |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457322b481908712a9630a17b954 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.