Triple
T8671669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YF-23 Black Widow II |
E205810
|
entity |
| Predicate | testPhase |
P22825
|
FINISHED |
| Object | flight test and evaluation |
—
|
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: flight test and evaluation | Statement: [YF-23 Black Widow II, testPhase, flight test and evaluation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testPhase Context triple: [YF-23 Black Widow II, testPhase, flight test and evaluation]
-
A.
programPhase
chosen
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
B.
targetsPhase
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
C.
missionPhaseTested
Indicates that a specific mission phase has been evaluated or validated through testing.
-
D.
testPilot
Indicates that an entity serves as a pilot responsible for testing and evaluating aircraft or related flight systems.
-
E.
scriptPhase
Indicates that one process, event, or component occurs during a particular stage or phase of a larger scripted or planned sequence.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491a34d08190b0795079d192a03d |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.