Triple
T33211751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IIIB |
E850180
|
entity |
| Predicate | launchesRole |
P52887
|
FINISHED |
| Object | polar orbit launches |
—
|
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: polar orbit launches | Statement: [Titan IIIB, launchesRole, polar orbit launches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchesRole Context triple: [Titan IIIB, launchesRole, polar orbit launches]
-
A.
launchPlatformRole
Indicates the functional role or responsibility an entity has in relation to a launch platform within a launch or deployment context.
-
B.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
C.
launchVehicleRole
chosen
Indicates the functional role or purpose that an entity serves in relation to a launch vehicle within a launch or mission context.
-
D.
launchAircraftRole
Indicates the role or function an entity has in initiating or carrying out the launch of an aircraft.
-
E.
startupRole
Indicates that an entity holds a specific role or position within a startup organization.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:30 a.m.