Triple
T21701921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijke tube |
E535677
|
entity |
| Predicate | oscillationType |
P39320
|
FINISHED |
| Object | longitudinal acoustic mode |
—
|
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: longitudinal acoustic mode | Statement: [Rijke tube, oscillationType, longitudinal acoustic mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oscillationType Context triple: [Rijke tube, oscillationType, longitudinal acoustic mode]
-
A.
dampingType
Indicates the specific kind or method of damping applied in a system or interaction between entities.
-
B.
waveType
chosen
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
OosterhoffType
Indicates the classification of a variable star based on its Oosterhoff type, reflecting characteristic differences in its pulsation properties and cluster population.
-
D.
cycleType
Indicates the specific kind or category of cycle involved in a repeated or cyclical process or relationship.
-
E.
tuningType
Indicates the specific method or configuration by which something is adjusted or calibrated to achieve a desired performance or behavior.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef9b802e008190a68ec62b98512794 |
completed | April 27, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:45 p.m.