Triple
T20469335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discovery One |
E502141
|
entity |
| Predicate | hasMissionObjective |
P3116
|
FINISHED |
| Object | investigate monolith near Jupiter |
—
|
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: investigate monolith near Jupiter | Statement: [Discovery One, hasMissionObjective, investigate monolith near Jupiter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMissionObjective Context triple: [Discovery One, hasMissionObjective, investigate monolith near Jupiter]
-
A.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
-
B.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
C.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
-
D.
hasMissionActivity
chosen
Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
-
E.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6995f753081909bbe03f7c251d9c1 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.