Triple
T26300592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/1980 S 25 |
E661544
|
entity |
| Predicate | trojanOf |
P28554
|
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: [S/1980 S 25, trojanOf, Tethys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trojanOf Context triple: [S/1980 S 25, trojanOf, Tethys]
-
A.
trojanMoonOf
chosen
Indicates that one celestial body shares an orbit with a larger body at a stable Lagrange point (typically leading or trailing it), acting as a Trojan moon of that body.
-
B.
firstTrojanEncounter
Indicates the initial meeting or interaction between an entity and a Trojan (e.g., a Trojan horse, malware, or Trojan-related force) in a given context.
-
C.
trapType
Indicates the specific kind or category of trap associated with an entity or situation.
-
D.
hijacked
Indicates that one entity has forcibly taken control of another entity, typically without authorization and against the will of its rightful controller.
-
E.
trap
Indicates that an entity captures, confines, or ensnares another entity, typically preventing its escape or movement.
- 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_69f60eb1ac9c8190a0b9193f4108dfbe |
completed | May 2, 2026, 2:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:15 p.m.