Triple
T18842446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ξ Persei |
E460829
|
entity |
| Predicate | rotationalVelocityProjected |
P69907
|
FINISHED |
| Object | about 200 km/s |
—
|
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 200 km/s | Statement: [ξ Persei, rotationalVelocityProjected, about 200 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationalVelocityProjected Context triple: [ξ Persei, rotationalVelocityProjected, about 200 km/s]
-
A.
hasRotationalVelocityKmPerSec
chosen
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
B.
hasRotationalVelocity
Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
-
C.
rotationAxis
Indicates the axis around which an object or system rotates or is intended to rotate.
-
D.
projectionAngle
Indicates the angle at which one entity is projected onto or relative to another reference (such as a line, plane, or direction).
-
E.
hasRotationCurve
Indicates that an object is associated with a rotation curve describing how its rotational velocity varies with radius or position.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.