Triple
T35719714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan II |
E1032436
|
entity |
| Predicate | operatorAsLaunchVehicle |
P110325
|
FINISHED |
| Object | U.S. Air Force |
—
|
NE NERFINISHED |
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: U.S. Air Force | Statement: [Titan II, operatorAsLaunchVehicle, U.S. Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAsLaunchVehicle Context triple: [Titan II, operatorAsLaunchVehicle, U.S. Air Force]
-
A.
launchVehicleRole
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
-
B.
launchVehicleUser
chosen
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
C.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
D.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
E.
usesLaunchVehiclesFrom
Indicates that one entity conducts its launches by employing launch vehicles that originate from or are provided by 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: May 3, 2026, 4:05 p.m.