Triple
T28361585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PMA-2 |
E718374
|
entity |
| Predicate | wasLaunchedWith |
P36266
|
FINISHED |
| Object | Space Shuttle Endeavour |
—
|
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: Space Shuttle Endeavour | Statement: [PMA-2, wasLaunchedWith, Space Shuttle Endeavour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLaunchedWith Context triple: [PMA-2, wasLaunchedWith, Space Shuttle Endeavour]
-
A.
launchedWith
chosen
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
B.
wasLaunchedForProgram
Indicates that an object (such as a mission or spacecraft) was launched specifically to serve or support a particular program.
-
C.
launchedVia
Indicates that an entity is initiated, deployed, or started by means of a specified method, mechanism, or intermediary.
-
D.
hasLaunch
Indicates that an entity initiates or carries out the launch of another entity (such as a product, mission, or event).
-
E.
launchedUnder
Indicates that one entity was initiated, started, or brought into operation under the authority, auspices, or framework of another entity (such as a program, organization, or policy).
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c3291888190a0f53f691269bbff |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:52 a.m.