Triple
T29998617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Launch program |
E762098
|
entity |
| Predicate | usedConvertedPlatformFrom |
P169343
|
FINISHED |
| Object | oil drilling rig Ocean Odyssey |
—
|
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: oil drilling rig Ocean Odyssey | Statement: [Sea Launch program, usedConvertedPlatformFrom, oil drilling rig Ocean Odyssey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedConvertedPlatformFrom Context triple: [Sea Launch program, usedConvertedPlatformFrom, oil drilling rig Ocean Odyssey]
-
A.
usedByPlatform
Indicates that something (such as a tool, component, or resource) is utilized or employed by a particular platform.
-
B.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
C.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
D.
usedOnPlatformType
Indicates that something is utilized or operates on a specific type of platform.
-
E.
adoptedPlatformOn
Indicates that an entity began using or officially adopted a particular platform on a specific date or point in time.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 6:40 p.m.