Triple
T34433785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claus process |
E883896
|
entity |
| Predicate | canBeFollowedBy |
P34869
|
FINISHED |
| Object | tail gas treating process |
—
|
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: tail gas treating process | Statement: [Claus process, canBeFollowedBy, tail gas treating process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeFollowedBy Context triple: [Claus process, canBeFollowedBy, tail gas treating process]
-
A.
mayBeFollowedBy
chosen
Indicates that one event, state, or item is allowed or able to occur immediately after another in a sequence.
-
B.
canBeConcludedWith
Indicates that one situation, process, or sequence is able to be finished, resolved, or brought to an end by another specified action or condition.
-
C.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
D.
followedByInSequence
Indicates that one event or element directly succeeds another in an ordered sequence.
-
E.
followedByInContext
Indicates that one element directly succeeds another within a specific contextual sequence or ordering.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 2 a.m.