Triple
T20326827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RR Lyrae variable star |
E492359
|
entity |
| Predicate | RRdCharacteristics |
P139704
|
FINISHED |
| Object | double-mode pulsators |
—
|
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: double-mode pulsators | Statement: [RR Lyrae variable star, RRdCharacteristics, double-mode pulsators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RRdCharacteristics Context triple: [RR Lyrae variable star, RRdCharacteristics, double-mode pulsators]
-
A.
ruleCharacteristics
Indicates the defining properties, constraints, or parameters that specify how a particular rule operates or should be applied.
-
B.
recordCharacteristic
Indicates that an entity documents or stores a specific characteristic or attribute of another entity.
-
C.
resultCharacterization
Indicates how the outcome of an event, process, or action is qualitatively described or characterized.
-
D.
rulesCharacteristic
Indicates that one entity establishes or defines a characteristic, property, or feature that another entity must follow or conform to.
-
E.
termCharacteristics
Indicates the defining properties, attributes, or features that characterize a given term.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:21 a.m.