Triple
T26982519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfvén waves |
E679640
|
entity |
| Predicate | compressibility |
P108191
|
FINISHED |
| Object | approximately incompressible |
—
|
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: approximately incompressible | Statement: [Alfvén waves, compressibility, approximately incompressible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compressibility Context triple: [Alfvén waves, compressibility, approximately incompressible]
-
A.
compressionCharacteristic
chosen
Indicates how an entity behaves or performs when subjected to compressive forces or pressure.
-
B.
compressionMode
Indicates the specific method or setting used to compress data or content in a given context.
-
C.
compressionType
Indicates the method or format used to compress data or content in the relationship.
-
D.
compressionRatio
Indicates the proportional reduction in size or volume achieved when something is compressed compared to its original size.
-
E.
compressionIgnition
Indicates that an engine or combustion process is initiated by compressing the fuel–air mixture until it self-ignites, rather than by an external spark.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 6:46 a.m.