Triple
T6287418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldebaran planetary system |
E140933
|
entity |
| Predicate | hostStarVariableType |
P29860
|
FINISHED |
| Object | slow irregular variable |
—
|
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: slow irregular variable | Statement: [Aldebaran planetary system, hostStarVariableType, slow irregular variable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostStarVariableType Context triple: [Aldebaran planetary system, hostStarVariableType, slow irregular variable]
-
A.
hostStarType
Indicates the classification of the star that serves as the primary host for an object, such as a planet or planetary system.
-
B.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
C.
variableStarType
chosen
Indicates the specific classification of variability that characterizes a variable star’s changing brightness.
-
D.
hostType
Indicates the category or kind of host associated with or responsible for the related entity or activity.
-
E.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.