Triple
T17359594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MINERVA |
E422031
|
entity |
| Predicate | deploymentConsequence |
P812
|
FINISHED |
| Object | escaped into heliocentric orbit |
—
|
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: escaped into heliocentric orbit | Statement: [MINERVA, deploymentConsequence, escaped into heliocentric orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploymentConsequence Context triple: [MINERVA, deploymentConsequence, escaped into heliocentric orbit]
-
A.
consequenceOfApplication
Indicates that something occurs as a result or outcome of a particular application or use of something.
-
B.
deploymentConcept
Indicates that one entity represents a concept, model, or plan that guides or defines how another entity is deployed or put into operation.
-
C.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
D.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
E.
announcedConsequence
Indicates that one entity has publicly stated or declared a specific outcome or consequence that will result from an action, event, or condition.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4be7448190988593ee342348c1 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.