Triple
T27655073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FGB |
E696970
|
entity |
| Predicate | wasLaunchedForProgram |
P163318
|
FINISHED |
| Object | International Space Station Program |
—
|
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: International Space Station Program | Statement: [FGB, wasLaunchedForProgram, International Space Station Program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLaunchedForProgram Context triple: [FGB, wasLaunchedForProgram, International Space Station Program]
-
A.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
B.
hasLaunchedFor
Indicates that an entity (such as a product, feature, or service) has been officially released or made available specifically for another entity (such as a user, group, market, or platform).
-
C.
programLaunch
Indicates the initiation or start of a software program or application.
-
D.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
-
E.
launchedVia
Indicates that an entity is initiated, deployed, or started by means of a specified method, mechanism, or intermediary.
- F. None of above. chosen
Provenance (4 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 2:33 p.m.