Triple
T868884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Bubble |
E18766
|
entity |
| Predicate | hasApproximateRadius |
P18961
|
FINISHED |
| Object | about 300 light-years |
—
|
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 300 light-years | Statement: [Local Bubble, hasApproximateRadius, about 300 light-years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateRadius Context triple: [Local Bubble, hasApproximateRadius, about 300 light-years]
-
A.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
approximateDiameter
Indicates that one entity specifies the estimated or rough measurement of another entity’s diameter.
-
C.
hasDimensionsApprox
chosen
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
D.
hasApproximateCoordinates
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
E.
hasPolarRadius
Indicates that an entity possesses a specific radius measured from its center to its pole, typically used for spheroidal or planetary bodies.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.