Triple
T18843119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta Scuti |
E460845
|
entity |
| Predicate | hasIntrinsicVariability |
P13845
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zeta Scuti, hasIntrinsicVariability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntrinsicVariability Context triple: [Zeta Scuti, hasIntrinsicVariability, true]
-
A.
hasVariability
chosen
Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
-
B.
hasVariabilityType
Indicates that an entity is associated with a specific kind or category of variability (e.g., how or in what way it varies).
-
C.
hasVariance
Indicates that there is a measurable degree of variability or dispersion in the values or outcomes associated with the related entities.
-
D.
hasDirectionVariability
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
E.
hasIndependentVariable
Indicates that one entity functions as the independent variable that influences or determines another entity in a relationship or experiment.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.