Triple
T2204799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IIIE-Centaur |
E50571
|
entity |
| Predicate | launchesTotal |
P7191
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Titan IIIE-Centaur, launchesTotal, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchesTotal Context triple: [Titan IIIE-Centaur, launchesTotal, 7]
-
A.
totalLaunches
chosen
Indicates the total number of times a particular entity has been launched or initiated.
-
B.
launchesTo
Indicates that one entity initiates the sending or propulsion of another entity toward a specific destination or into a particular trajectory.
-
C.
successfulLaunches
Indicates that one entity has carried out one or more launches that achieved their intended objectives without failure.
-
D.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
E.
helpedLaunch
Indicates that one entity played a significant role in initiating, starting, or bringing another entity (such as a project, product, or organization) into operation or public release.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.