Triple
T24105447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E ring of Saturn |
E597207
|
entity |
| Predicate | peakDensityNear |
P7612
|
FINISHED |
| Object | orbit of Enceladus |
—
|
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: orbit of Enceladus | Statement: [E ring of Saturn, peakDensityNear, orbit of Enceladus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDensityNear Context triple: [E ring of Saturn, peakDensityNear, orbit of Enceladus]
-
A.
peakApproximateMa
Indicates that one entity’s peak value is approximately equal to another entity’s peak value.
-
B.
clusterDensity
Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
-
C.
hasNearbySettlementDensity
Indicates that an entity is associated with a concentration of settlements located within a nearby surrounding area.
-
D.
suggestsFrequencyNear
Indicates that one entity proposes or implies an approximate or nearby frequency value relative to another entity.
-
E.
hasNearbyPeak
chosen
Indicates that one location has another peak situated close to it in geographic space.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de154388819084f5a3f2b139287a |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:01 p.m.