Triple
T29939472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haber–Bosch process |
E760454
|
entity |
| Predicate | usesPromoter |
P180248
|
FINISHED |
| Object | potassium oxide |
—
|
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: potassium oxide | Statement: [Haber–Bosch process, usesPromoter, potassium oxide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPromoter Context triple: [Haber–Bosch process, usesPromoter, potassium oxide]
-
A.
usesPromotion
Indicates that an entity applies or takes advantage of a specific promotion, discount, or special offer.
-
B.
usesPromotionFrom
Indicates that one entity applies or benefits from a promotion, discount, or marketing offer provided or originated by another entity.
-
C.
promotesUseIn
Indicates that one entity actively encourages, supports, or increases the adoption or application of another entity within a particular context or setting.
-
D.
promotedWith
Indicates that one entity is advertised, marketed, or publicized together with another entity as part of the same promotional effort.
-
E.
hasNotablePromoter
Indicates that an entity is actively supported, publicized, or championed by a notable promoter.
- 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_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
| PDg | Predicate description generation | batch_69f739a58b3c81908abc2b8738a65678 |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 29, 2026, 6:22 p.m.