Triple
T12175798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolf–Rayet star |
E290082
|
entity |
| Predicate | WO star |
P64835
|
FINISHED |
| Object | oxygen-sequence Wolf–Rayet star |
—
|
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: oxygen-sequence Wolf–Rayet star | Statement: [Wolf–Rayet star, WO star, oxygen-sequence Wolf–Rayet star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WO star Context triple: [Wolf–Rayet star, WO star, oxygen-sequence Wolf–Rayet star]
-
A.
starIs
Indicates that one entity is identified or classified as a star in relation to another entity or context.
-
B.
star
Indicates that an entity has been given a special or highlighted status, often marking it as important, featured, or favorited in relation to others.
-
C.
starType
chosen
Indicates the classification relationship specifying what type or category of star an astronomical object is.
-
D.
isPrimaryStarOf
Indicates that a star serves as the main or central stellar object in relation to a specified system, object, or context.
-
E.
stars
Indicates that one entity marks, highlights, or designates another as special, important, or featured (often by assigning a star or similar marker).
- 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.