Triple
T7272906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Ceti f |
E161147
|
entity |
| Predicate | radialVelocityAmplitude |
P76149
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Tau Ceti f, radialVelocityAmplitude, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radialVelocityAmplitude Context triple: [Tau Ceti f, radialVelocityAmplitude, low]
-
A.
hasRadialVelocity_km_per_s
Indicates that one entity has a measured radial velocity, expressed in kilometers per second, relative to another reference frame or object.
-
B.
lightcurveAmplitude
Indicates the measured range of brightness variation of an object over time in its light curve.
-
C.
hasLightcurveAmplitude
Indicates the measured range of brightness variation (amplitude) in an object's lightcurve over time.
-
D.
hasRadialVelocityDispersion
Indicates that an entity exhibits a spread in its radial velocities, quantifying how much the line-of-sight speeds of its components differ from one another.
-
E.
hasRadialVelocitySignature
Indicates that an object exhibits a measurable radial velocity pattern characteristic of a specific physical process or source.
- F. None of above. chosen
Provenance (4 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 2:58 p.m.