Triple
T20326810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RR Lyrae variable star |
E492359
|
entity |
| Predicate | variabilityCause |
P694
|
FINISHED |
| Object | radial pulsation |
—
|
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: radial pulsation | Statement: [RR Lyrae variable star, variabilityCause, radial pulsation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variabilityCause Context triple: [RR Lyrae variable star, variabilityCause, radial pulsation]
-
A.
hasVariability
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
B.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
D.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
E.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e4130081909ec54f131939e442 |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:21 a.m.