Triple
T26300498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saturn XIII |
E661541
|
entity |
| Predicate | isTrojanOf |
P160224
|
FINISHED |
| Object | Tethys |
—
|
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: Tethys | Statement: [Saturn XIII, isTrojanOf, Tethys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTrojanOf Context triple: [Saturn XIII, isTrojanOf, Tethys]
-
A.
isSuspiciousOf
Indicates that one entity believes another entity or situation may be untrustworthy, harmful, or involved in wrongdoing.
-
B.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
C.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
D.
usesTivraMa
Indicates that one entity makes use of or employs TivraMa in performing an action or fulfilling a function.
-
E.
isADROf
Indicates a relationship where one entity serves as the Authorized Designated Responsible Officer (ADRO) for another entity, typically bearing formal oversight or accountability on its behalf.
- F. None of above. chosen
Provenance (4 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_69f60eb1ac9c8190a0b9193f4108dfbe |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:15 p.m.