Triple
T26412651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethys Trojan moons |
E664001
|
entity |
| Predicate | wereDiscoveredBy |
P412
|
FINISHED |
| Object | Cassini–Huygens mission (via imaging) |
—
|
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: Cassini–Huygens mission (via imaging) | Statement: [Tethys Trojan moons, wereDiscoveredBy, Cassini–Huygens mission (via imaging)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereDiscoveredBy Context triple: [Tethys Trojan moons, wereDiscoveredBy, Cassini–Huygens mission (via imaging)]
-
A.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
B.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
C.
eraOfDiscovery
Indicates a relationship where something belongs to, occurs in, or is characteristic of a specific era of discovery or exploration.
-
D.
eponymOfDiscovererOf
Indicates that one entity gives its name to the person who discovered another entity.
-
E.
causeOfDiscovery
Indicates that one entity is the reason or factor that led to the discovery of another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611325fd48190898639883fb113fd |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:39 p.m.