Triple
T25859310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunyaev–Zel’dovich effect |
E651437
|
entity |
| Predicate | redshiftIndependenceReason |
P243
|
FINISHED |
| Object | surface brightness conservation |
—
|
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: surface brightness conservation | Statement: [Sunyaev–Zel’dovich effect, redshiftIndependenceReason, surface brightness conservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redshiftIndependenceReason Context triple: [Sunyaev–Zel’dovich effect, redshiftIndependenceReason, surface brightness conservation]
-
A.
independenceFrom
chosen
Indicates that one entity is not controlled, governed, or significantly influenced by another entity.
-
B.
stabilityReason
Indicates the factor, condition, or cause that accounts for why something remains stable or unchanged.
-
C.
hasAutonomyReason
Indicates that an entity has a specific reason or justification for its autonomy or independent decision-making.
-
D.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
E.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an entity.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026a80208190a8b1fae20d6ed906 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 8:04 a.m.