Triple
T609460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K4s Pacific |
E12064
|
entity |
| Predicate | boilerPressure |
P4265
|
FINISHED |
| Object | 205 psi |
—
|
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: 205 psi | Statement: [K4s Pacific, boilerPressure, 205 psi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boilerPressure Context triple: [K4s Pacific, boilerPressure, 205 psi]
-
A.
overallPressureRatio
Indicates the ratio between the total outlet pressure and the total inlet pressure across a component or system, reflecting how much the pressure is increased or decreased overall.
-
B.
pressureAtBottom
chosen
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
-
C.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
D.
temperatureControlMethod
Indicates the method or mechanism used to regulate or maintain a desired temperature.
-
E.
hasAtmosphericPressureAtSeaLevel
Indicates that an entity possesses a specific value of atmospheric pressure measured at sea level.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df68f2c8190a0ee9da4692b2a62 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cfa7b4481909bec7a5fd3e98c65 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.