Triple
T26300485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys |
E661540
|
entity |
| Predicate | hasTrojanGroup |
P28554
|
FINISHED |
| Object | Tethys Trojan group |
—
|
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 Trojan group | Statement: [Tethys, hasTrojanGroup, Tethys Trojan group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrojanGroup Context triple: [Tethys, hasTrojanGroup, Tethys Trojan group]
-
A.
isTrojanOf
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.
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.
-
C.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
D.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
-
E.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
- 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_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 26, 2026, 10:15 p.m.