Triple
T633451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuiper Belt object |
E15968
|
entity |
| Predicate | hasDiameterRange |
P7302
|
FINISHED |
| Object | few kilometers to over 2000 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: few kilometers to over 2000 kilometers | Statement: [Kuiper Belt object, hasDiameterRange, few kilometers to over 2000 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiameterRange Context triple: [Kuiper Belt object, hasDiameterRange, few kilometers to over 2000 kilometers]
-
A.
approximateDiameter
chosen
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
B.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
C.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
D.
coreStageDiameter
Indicates the diameter measurement of the central or primary stage of an object or system.
-
E.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec3b6488190aa0dce216c089a2e |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.