Triple
T12175783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolf–Rayet star |
E290082
|
entity |
| Predicate | hasTerminalWindVelocity |
P60166
|
FINISHED |
| Object | 1000 to 5000 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: 1000 to 5000 km/s | Statement: [Wolf–Rayet star, hasTerminalWindVelocity, 1000 to 5000 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalWindVelocity Context triple: [Wolf–Rayet star, hasTerminalWindVelocity, 1000 to 5000 km/s]
-
A.
hasTypicalVelocity
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
B.
windSpeed
chosen
Indicates the measured or estimated rate at which wind is moving at a given location and time.
-
C.
hasWindPattern
Indicates that one entity exhibits, is characterized by, or is associated with a particular pattern of wind behavior.
-
D.
usesWindTunnelOf
Indicates that one entity makes use of another entity’s wind tunnel facility for testing, experimentation, or related aerodynamic activities.
-
E.
windResistance
Indicates the degree to which an entity opposes or reduces the effect of wind acting upon it.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.