Triple
T28695086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolinella |
E729390
|
entity |
| Predicate | firstIsolatedFrom |
P202070
|
FINISHED |
| Object | bovine rumen |
—
|
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: bovine rumen | Statement: [Wolinella, firstIsolatedFrom, bovine rumen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIsolatedFrom Context triple: [Wolinella, firstIsolatedFrom, bovine rumen]
-
A.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
B.
isIsolated
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
-
C.
isolateFrom
Indicates that one entity is separated or kept apart from another entity or source.
-
D.
firstHostIsolatedFrom
Indicates that the first host is separated or kept apart from the referenced entity, with no direct interaction or connection between them.
-
E.
wasFirstIsolatedInYear
Indicates that the first successful isolation or identification of an entity occurred in the specified year.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
| PDg | Predicate description generation | batch_6a004c41009c8190b18e41acf1fd7372 |
completed | May 10, 2026, 9:13 a.m. |
Created at: April 28, 2026, 5:39 a.m.