Triple
T38209982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Com noise reduction |
E1010511
|
entity |
| Predicate | expansionRatio |
P21083
|
FINISHED |
| Object | 1:2 |
—
|
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: 1:2 | Statement: [High Com noise reduction, expansionRatio, 1:2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionRatio Context triple: [High Com noise reduction, expansionRatio, 1:2]
-
A.
expansionNumber
Indicates the specific expansion sequence or identifier assigned to an entity within a series of related additions or extensions.
-
B.
expansionParameter
Indicates a parameter that controls or characterizes how something expands, such as the rate, extent, or manner of its expansion.
-
C.
nozzleExpansionRatio
chosen
Indicates the ratio between a nozzle’s exit area and its throat area, describing how much the flow expands as it passes through the nozzle.
-
D.
expansionOrContraction
Indicates a change in size, volume, or extent of something, whether it is increasing (expanding) or decreasing (contracting).
-
E.
expansionPotential
Indicates the capacity or likelihood for something to grow, extend, or increase beyond its current scope or state.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:30 p.m.