Triple
T13044875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putrid Sea |
E327290
|
entity |
| Predicate | odorCause |
P694
|
FINISHED |
| Object | hydrogen sulfide emissions |
—
|
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: hydrogen sulfide emissions | Statement: [Putrid Sea, odorCause, hydrogen sulfide emissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odorCause Context triple: [Putrid Sea, odorCause, hydrogen sulfide emissions]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
odor
Indicates that one entity emits, possesses, or is characterized by a particular smell detectable by another entity.
-
C.
odorResponse
Indicates a relationship where an entity exhibits a measurable reaction or change in behavior, physiology, or activity in response to an odor stimulus.
-
D.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
E.
eligibleCause
Indicates that one entity qualifies as a valid or acceptable cause or reason for another entity or outcome.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:56 p.m.