Triple
T26300524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn XIII |
E661541
|
entity |
| Predicate | hasCompanionTrojan |
P160224
|
FINISHED |
| Object | Calypso |
—
|
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: Calypso | Statement: [Saturn XIII, hasCompanionTrojan, Calypso]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompanionTrojan Context triple: [Saturn XIII, hasCompanionTrojan, Calypso]
-
A.
isTrojanOf
chosen
Indicates that one entity is a Trojan (e.g., a malicious or deceptive program or component) specifically associated with, derived from, or targeting another entity.
-
B.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
-
C.
hasCompanionCore
Indicates that an entity is associated with, or accompanied by, a specific companion core.
-
D.
hasCompanionPiece
Indicates that one item is conceptually or functionally paired with another item as its companion piece.
-
E.
hasCompanionCandidate
Indicates that an entity is associated with another entity that is being considered or proposed as a potential companion.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 26, 2026, 10:15 p.m.