Triple
T24105451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E ring of Saturn |
E597207
|
entity |
| Predicate | particleSizeRange |
P97532
|
FINISHED |
| Object | submicrometer to several micrometers |
—
|
LITERAL FINISHED |
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: submicrometer to several micrometers | Statement: [E ring of Saturn, particleSizeRange, submicrometer to several micrometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: particleSizeRange Context triple: [E ring of Saturn, particleSizeRange, submicrometer to several micrometers]
-
A.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
B.
typicalSedimentSizeRange
chosen
Indicates the usual range of sediment particle sizes associated with an entity or environment.
-
C.
clusterSizeRange
Indicates the range of allowable or observed sizes for a given cluster within a specified context.
-
D.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
E.
divisionSize
Indicates the size or magnitude of a division or subdivided part in relation to a whole.
- 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.