Triple
T29939506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haber–Bosch process |
E760454
|
entity |
| Predicate | usesSeparationStep |
P81466
|
FINISHED |
| Object | ammonia condensation |
—
|
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: ammonia condensation | Statement: [Haber–Bosch process, usesSeparationStep, ammonia condensation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSeparationStep Context triple: [Haber–Bosch process, usesSeparationStep, ammonia condensation]
-
A.
usedToSeparate
Indicates that one entity serves as a means or tool to divide, isolate, or keep other entities apart from each other.
-
B.
separationProcess
chosen
Indicates a process in which components of a mixture or system are divided or isolated from one another based on differing properties or conditions.
-
C.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
D.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
E.
separationPhase
Indicates the phase or stage during which two previously connected entities are being separated or detached from one another.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 29, 2026, 6:22 p.m.