Triple
T11515361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Tor |
E273016
|
entity |
| Predicate | hasVogesProskauerReaction |
P99891
|
FINISHED |
| Object | positive |
—
|
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: positive | Statement: [El Tor, hasVogesProskauerReaction, positive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVogesProskauerReaction Context triple: [El Tor, hasVogesProskauerReaction, positive]
-
A.
ringReaction
Indicates that one entity performs or undergoes a reaction involving a chemical ring structure in relation to another entity.
-
B.
hasVow
Indicates that one entity has made or is bound by a formal vow or promise in relation to another entity or context.
-
C.
decarboxylationProduct
Indicates the product that results from a decarboxylation reaction in which a carboxyl group is removed from a substrate.
-
D.
isFormulatedUsing
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
E.
fusionReactionExample
Indicates that one entity serves as an example or instance of a specific fusion reaction involving the other entity.
- 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db8bf9c8190820c289e6b0c3873 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.