Triple
T24248906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herschel crater |
E603456
|
entity |
| Predicate | relativeSizeToMimasRadius |
P155327
|
FINISHED |
| Object | about half of Mimas’s radius |
—
|
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: about half of Mimas’s radius | Statement: [Herschel crater, relativeSizeToMimasRadius, about half of Mimas’s radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSizeToMimasRadius Context triple: [Herschel crater, relativeSizeToMimasRadius, about half of Mimas’s radius]
-
A.
relativeSizeToEarth
Indicates the comparative size of an entity when measured relative to the size of Earth.
-
B.
relativeSizeInSaturnSystem
Indicates the comparative size relationship of an object relative to other objects within the Saturn system.
-
C.
relativeSizeToPluto
Indicates how the size of one entity compares to the size of Pluto.
-
D.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
-
E.
earthToMoonRadiusRatio
Indicates the proportional relationship between the radius of the Earth and the radius of the Moon.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b87d03c8190a38ca0c0b65ce6fc |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:04 a.m.