Triple
T365128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandrasekhar–Friedman–Schutz instability |
E7942
|
entity |
| Predicate | stabilizedBy |
P12760
|
FINISHED |
| Object | viscosity in stellar matter |
—
|
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: viscosity in stellar matter | Statement: [Chandrasekhar–Friedman–Schutz instability, stabilizedBy, viscosity in stellar matter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stabilizedBy Context triple: [Chandrasekhar–Friedman–Schutz instability, stabilizedBy, viscosity in stellar matter]
-
A.
isStable
Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
-
B.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
-
C.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
D.
annexedBy
Indicates that one entity has been incorporated into and brought under the control or sovereignty of another entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe6c1b4819083335e880c205ed6 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eafc8da88190b4a05182f4384442 |
completed | Feb. 28, 2026, 1:17 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.