Triple
T16318608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escherichia coli OP50 |
E396233
|
entity |
| Predicate | usedAsControlIn |
P2506
|
FINISHED |
| Object | microbiome manipulation experiments in C. elegans |
—
|
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: microbiome manipulation experiments in C. elegans | Statement: [Escherichia coli OP50, usedAsControlIn, microbiome manipulation experiments in C. elegans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsControlIn Context triple: [Escherichia coli OP50, usedAsControlIn, microbiome manipulation experiments in C. elegans]
-
A.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
B.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
C.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
D.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b3e3e081908a996b3e57ca4e32 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.