Triple
T4617793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open cluster M25 |
E100907
|
entity |
| Predicate | containsVariableStarType |
P29860
|
FINISHED |
| Object | Cepheid 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: Cepheid variable | Statement: [Open cluster M25, containsVariableStarType, Cepheid variable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsVariableStarType Context triple: [Open cluster M25, containsVariableStarType, Cepheid variable]
-
A.
variableStarType
chosen
Indicates the specific classification of variability that characterizes a variable star’s changing brightness.
-
B.
hasVariable
Indicates that one entity includes, defines, or is associated with a particular variable.
-
C.
hasVarianceSymbol
Indicates that one entity is associated with, or represented by, a specific variance symbol in a mathematical or statistical context.
-
D.
variableType
Indicates that one entity is the type or data category of the other entity, which is a variable.
-
E.
isAllStarTypeSelection
Indicates that an entity has been selected as part of an All-Star type group or roster.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.