Triple
T909594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northrop X-4 Bantam |
E19627
|
entity |
| Predicate | programGoal |
P1415
|
FINISHED |
| Object | evaluate tailless swept-wing design near Mach 1 |
—
|
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: evaluate tailless swept-wing design near Mach 1 | Statement: [Northrop X-4 Bantam, programGoal, evaluate tailless swept-wing design near Mach 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programGoal Context triple: [Northrop X-4 Bantam, programGoal, evaluate tailless swept-wing design near Mach 1]
-
A.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
B.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
C.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
D.
hasPrimaryGoal
chosen
Indicates that an entity’s main or most important objective is the specified goal.
-
E.
programOutcome
Indicates the resulting state, effect, or consequence produced by executing or completing a program.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2f605bc8190a5245aa2ca55cf43 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b2918ea881908698020b995a8eae |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.