Triple
T22983941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leavitt law |
E571548
|
entity |
| Predicate | accuracyImprovedBy |
P130190
|
FINISHED |
| Object | observations in infrared bands |
—
|
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: observations in infrared bands | Statement: [Leavitt law, accuracyImprovedBy, observations in infrared bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accuracyImprovedBy Context triple: [Leavitt law, accuracyImprovedBy, observations in infrared bands]
-
A.
hasImproved
chosen
Indicates that an entity’s state, quality, or performance has become better compared to a previous point in time.
-
B.
improvesOn
Indicates that one entity enhances, refines, or performs better than another entity, typically by addressing its limitations or increasing its effectiveness.
-
C.
curacy
Indicates that one entity serves in the role or position of a curate (assistant clergy) in relation to another entity, typically a parish or church.
-
D.
performanceImprovementReason
Indicates the reason or cause behind an observed or intended improvement in performance.
-
E.
seeksToImprove
Indicates an intentional effort by one entity to make another entity or condition better than its current state.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829775e881909c5d6d35d3fd57f7 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.