Triple
T36703542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCM-2 |
E906294
|
entity |
| Predicate | carriedOnMission |
P89381
|
FINISHED |
| Object | Oceansat-2 mission |
—
|
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: Oceansat-2 mission | Statement: [OCM-2, carriedOnMission, Oceansat-2 mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedOnMission Context triple: [OCM-2, carriedOnMission, Oceansat-2 mission]
-
A.
operatedOnMission
Indicates that an agent carried out or participated in the execution of a specific mission.
-
B.
carriedOutMissionIn
Indicates that an entity performed or executed a specific mission in a particular context or location.
-
C.
performedMission
chosen
Indicates that an agent has carried out or completed a specific mission or task.
-
D.
partOfMission
Indicates that one entity is a component, phase, or element belonging to or included within a larger mission.
-
E.
namedForMission
Indicates that something (such as an object, place, or project) is given a name in honor of or derived from a particular mission.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c80d4ba48190bf6beb2c9b108be1 |
completed | May 3, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.