Triple
T21123557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-20 Dyna-Soar |
E520492
|
entity |
| Predicate | intendedMissionType |
P22637
|
FINISHED |
| Object | military space operations |
—
|
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: military space operations | Statement: [X-20 Dyna-Soar, intendedMissionType, military space operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMissionType Context triple: [X-20 Dyna-Soar, intendedMissionType, military space operations]
-
A.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
B.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
typeOfMissionSupport
Indicates the kind or category of support provided in relation to a specific mission.
-
D.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
E.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72236b2d88190bef9f0cd6924ca92 |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:55 p.m.