Triple
T29939469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haber–Bosch process |
E760454
|
entity |
| Predicate | operatesAtHigh |
P199484
|
FINISHED |
| Object | 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: pressure | Statement: [Haber–Bosch process, operatesAtHigh, pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAtHigh Context triple: [Haber–Bosch process, operatesAtHigh, pressure]
-
A.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
B.
highReCharacteristic
Indicates that an entity exhibits a high Reynolds number characteristic, typically implying flow dominated by inertial rather than viscous forces.
-
C.
isHighPerformance
Indicates that an entity operates at a superior or above-standard level of efficiency, speed, or capability compared to typical expectations or benchmarks.
-
D.
operationalPeak
Indicates the highest level or period of performance, capacity, or activity that a system, process, or entity reaches during its operation.
-
E.
effectAtHighSpeed
Indicates that the effect or outcome occurs specifically when the subject is moving or operating at high speed.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
| PDg | Predicate description generation | batch_69ff3e16527c81908c8d89da704ce012 |
completed | May 9, 2026, 2 p.m. |
Created at: April 29, 2026, 6:22 p.m.