Triple
T26412690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys |
E664001
|
entity |
| Predicate | hasTrojanMoons |
P181027
|
FINISHED |
| Object | Telesto |
—
|
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: Telesto | Statement: [Tethys, hasTrojanMoons, Telesto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrojanMoons Context triple: [Tethys, hasTrojanMoons, Telesto]
-
A.
hasIrregularMoon
Indicates that an astronomical body possesses at least one moon with an irregular, typically highly inclined or eccentric, orbit.
-
B.
hasApproximateNumberOfKnownMoons
Indicates that an entity is associated with an estimated or non-exact count of moons known to orbit it.
-
C.
hasDiscoveredMoonOf
Indicates that one entity is the discoverer of a moon that orbits another entity (typically a planet or celestial body).
-
D.
hasNumberOfKnownMoons
Indicates the relationship that specifies how many moons are known to orbit a given celestial body.
-
E.
hasNotableMoon
Indicates that an entity possesses a moon that is distinguished by particular significance, prominence, or interest.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 26, 2026, 11:39 p.m.