Triple
T29998616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Launch program |
E762098
|
entity |
| Predicate | usedSupportVessel |
P26083
|
FINISHED |
| Object | Sea Launch Commander |
—
|
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: Sea Launch Commander | Statement: [Sea Launch program, usedSupportVessel, Sea Launch Commander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSupportVessel Context triple: [Sea Launch program, usedSupportVessel, Sea Launch Commander]
-
A.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
B.
hasVessel
chosen
Indicates that one entity possesses, uses, or is associated with a particular vessel (such as a container, ship, or transport medium) in the context of the described relationship or action.
-
C.
usesVesselsOperatedBy
Indicates that one entity makes use of vessels that are operated or controlled by another entity.
-
D.
vesselService
Indicates a service relationship in which one entity provides, operates, or maintains a vessel (such as a ship or boat) for another entity.
-
E.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794cf5848190a60ca2c4d9f50098 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:40 p.m.