Triple
T30527830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma Doradus |
E776904
|
entity |
| Predicate | discoveryOfVariability |
P148078
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Gamma Doradus, discoveryOfVariability, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOfVariability Context triple: [Gamma Doradus, discoveryOfVariability, 1990s]
-
A.
variabilityRecognizedIn
chosen
Indicates that variability or variation in one entity is acknowledged, identified, or detected within the context of another entity.
-
B.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
C.
hasCauseOfVariability
Indicates a relationship where one factor or condition is identified as the source or driver of variation observed in another.
-
D.
hasSpectralVariability
Indicates that an entity exhibits changes or fluctuations in its spectral properties over time or under different conditions.
-
E.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
- 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 8:17 p.m.