Triple
T11993180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newcomen atmospheric engine |
E285462
|
entity |
| Predicate | typicalPressure |
P102766
|
FINISHED |
| Object | slightly above atmospheric pressure |
—
|
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: slightly above atmospheric pressure | Statement: [Newcomen atmospheric engine, typicalPressure, slightly above atmospheric pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPressure Context triple: [Newcomen atmospheric engine, typicalPressure, slightly above atmospheric pressure]
-
A.
pressureRange
Indicates the range of pressure values within which a condition, process, or relationship is defined or valid.
-
B.
typicalTemperature
Indicates the usual or characteristic temperature associated with an entity under normal conditions.
-
C.
pressureFrom
Indicates a relationship where one entity exerts influence, coercion, or force on another to affect its decisions, actions, or state.
-
D.
operatingPressureStandard
Indicates the standard or specified pressure level at which an operation, system, or component is intended to function.
-
E.
chamberPressure_bar
Indicates the pressure within a chamber, expressed in units of bar.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903b11ac481909866b611380792e7 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.