Triple
T156169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun |
E3186
|
entity |
| Predicate | equatorialRadius |
P2017
|
FINISHED |
| Object | approximately 695700 kilometers |
—
|
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: approximately 695700 kilometers | Statement: [Sun, equatorialRadius, approximately 695700 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equatorialRadius Context triple: [Sun, equatorialRadius, approximately 695700 kilometers]
-
A.
hasEquatorialRadius
chosen
Indicates that an entity has a specified radius measured at its equator.
-
B.
hasEquatorialCircumference
Indicates that one entity has a specified measurement for its circumference at the equator.
-
C.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
D.
hasAxialTilt
Indicates that one celestial body’s rotational axis is tilted at a certain angle relative to its orbital plane around another body.
-
E.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.