Triple
T23524435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan 34D |
E574593
|
entity |
| Predicate | launchSitesPrimaryUser |
P44497
|
FINISHED |
| Object | United States 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: United States Air Force | Statement: [Titan 34D, launchSitesPrimaryUser, United States Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSitesPrimaryUser Context triple: [Titan 34D, launchSitesPrimaryUser, United States Air Force]
-
A.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
B.
launchSites
chosen
Indicates locations from which an object, mission, or vehicle is launched or initiated.
-
C.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
D.
launchSiteCode
Indicates the code that identifies the site or location from which a launch takes place.
-
E.
servesLaunchSite
Indicates that one entity functions as the launch site used by another entity for initiating launches.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac72bfb88190b7da3837e66e851c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.