Triple
T35492062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostwald process |
E1025755
|
entity |
| Predicate | feedstockFor |
P104219
|
FINISHED |
| Object | ammonium nitrate production |
—
|
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: ammonium nitrate production | Statement: [Ostwald process, feedstockFor, ammonium nitrate production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feedstockFor Context triple: [Ostwald process, feedstockFor, ammonium nitrate production]
-
A.
feedsReservoir
Indicates that one entity supplies or channels a flow (such as water or another resource) into a reservoir.
-
B.
usesFeedstock
chosen
Indicates that one entity employs or consumes another entity as a raw material or input resource in a process or operation.
-
C.
mainFeederOf
Indicates that one entity serves as the primary source or supplier of resources, energy, or input to another entity.
-
D.
feedsOrDrains
Indicates that one entity supplies resources or energy to another or removes them from it, acting as either a source (feeds) or a sink (drains).
-
E.
feedSystem
Indicates that one entity supplies or provides input, resources, or data into another entity or system for its operation or processing.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.