Triple
T19931807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9 Sagittarii |
E479070
|
entity |
| Predicate | drivesStellarWindBubble |
P68085
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [9 Sagittarii, drivesStellarWindBubble, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivesStellarWindBubble Context triple: [9 Sagittarii, drivesStellarWindBubble, yes]
-
A.
hasStellarWind
chosen
Indicates that an astronomical object emits a continuous outflow of gas or charged particles, known as a stellar wind, into the surrounding space.
-
B.
usesWindTunnelOf
Indicates that one entity makes use of another entity’s wind tunnel facility for testing, experimentation, or related aerodynamic activities.
-
C.
stellarWindTerminalVelocity
Indicates the final, asymptotic speed reached by a star’s stellar wind far from the star, after it has been fully accelerated.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
blowsAcross
Indicates that something (typically wind, air, or a current) moves across or over another entity or area, passing from one side or region to another.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a13ebc08190a583aa4c5e9f6648 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.