Triple
T4619111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaus Media |
E100935
|
entity |
| Predicate | hasRadialVelocity |
P8103
|
FINISHED |
| Object | receding from Sun |
—
|
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: receding from Sun | Statement: [Kaus Media, hasRadialVelocity, receding from Sun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadialVelocity Context triple: [Kaus Media, hasRadialVelocity, receding from Sun]
-
A.
hasTypicalVelocity
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
B.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
C.
hasEscapeVelocity
Indicates that an object or body possesses a velocity sufficient to overcome the gravitational pull of another body without further propulsion.
-
D.
velocityRelativeToSun
chosen
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
-
E.
properMotion
Indicates the apparent angular movement of an astronomical object across the sky relative to distant background objects over time.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.