Triple
T21701905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijke tube |
E535677
|
entity |
| Predicate | wireMeshFunction |
P144966
|
FINISHED |
| Object | periodic heating of passing air |
—
|
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: periodic heating of passing air | Statement: [Rijke tube, wireMeshFunction, periodic heating of passing air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wireMeshFunction Context triple: [Rijke tube, wireMeshFunction, periodic heating of passing air]
-
A.
numberOfWires
Indicates the quantity of wires associated with or contained in a given entity.
-
B.
isWired
Indicates that one entity is physically connected to another via electrical or data wiring.
-
C.
wireDistance
Indicates the physical separation or length of wire between two connected points or components.
-
D.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
E.
fiberwiseDescription
Indicates a description or characterization that is given separately for each fiber in a fibered or parameterized structure, specifying how the relationship or action behaves over individual fibers.
- 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_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. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:45 p.m.