Triple
T156167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun |
E3186
|
entity |
| Predicate | radius |
P2019
|
FINISHED |
| Object | approximately 696340 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 696340 kilometers | Statement: [Sun, radius, approximately 696340 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radius Context triple: [Sun, radius, approximately 696340 kilometers]
-
A.
hasMeanRadius
chosen
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
C.
radiusOfSevereDestruction
Indicates the distance from a central point within which damage or destruction is expected to be extremely severe.
-
D.
zone
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
E.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
- 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.