Triple
T21954693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jupiter 2 |
E542155
|
entity |
| Predicate | threatEncounteredOnboard |
P50110
|
FINISHED |
| Object | space spiders |
—
|
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: space spiders | Statement: [Jupiter 2, threatEncounteredOnboard, space spiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatEncounteredOnboard Context triple: [Jupiter 2, threatEncounteredOnboard, space spiders]
-
A.
threatContained
Indicates that an identified threat has been successfully neutralized, controlled, or otherwise prevented from causing further harm or escalation.
-
B.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
C.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
D.
transportThreat
Indicates a relationship where an entity moves or conveys a threat from one place or context to another.
-
E.
threatStatusSystem
Indicates the classification framework or system used to assign a conservation or threat status to an entity.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243f46dc819097e4a1849af7fba4 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.