Triple
T27343511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantis (OV-104) |
E684170
|
entity |
| Predicate | performedMissionType |
P22637
|
FINISHED |
| Object | satellite deployment |
—
|
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: satellite deployment | Statement: [Atlantis (OV-104), performedMissionType, satellite deployment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedMissionType Context triple: [Atlantis (OV-104), performedMissionType, satellite deployment]
-
A.
performedMission
Indicates that an agent has carried out or completed a specific mission or task.
-
B.
performsMissionFor
Indicates that one entity carries out or executes a mission on behalf of, or under the direction of, another entity.
-
C.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
D.
carriedOutMissionIn
Indicates that an entity performed or executed a specific mission in a particular context or location.
-
E.
operatedOnMission
Indicates that an agent carried out or participated in the execution of a specific 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 11:44 a.m.