Triple
T4637339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bell X-1B |
E101563
|
entity |
| Predicate | programObjective |
P49728
|
FINISHED |
| Object | extend knowledge of flight beyond Mach 2 |
—
|
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: extend knowledge of flight beyond Mach 2 | Statement: [Bell X-1B, programObjective, extend knowledge of flight beyond Mach 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programObjective Context triple: [Bell X-1B, programObjective, extend knowledge of flight beyond Mach 2]
-
A.
educationalObjective
Indicates the intended learning goal, skill, or competency that an educational resource, activity, or program is designed to achieve.
-
B.
trainingObjective
Indicates the goal or target outcome that a training process is designed to achieve.
-
C.
usesObjective
Indicates that an agent employs or applies a particular object, tool, or resource to carry out an action or achieve a goal.
-
D.
engineeringGoal
chosen
Indicates that an entity has a specific engineering-related objective, target, or desired outcome it is intended to achieve or support.
-
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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.