Triple
T25111504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alvin John Clark |
E629005
|
entity |
| Predicate | usedResearchModel |
P157654
|
FINISHED |
| Object | bacteriophages |
—
|
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: bacteriophages | Statement: [Alvin John Clark, usedResearchModel, bacteriophages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedResearchModel Context triple: [Alvin John Clark, usedResearchModel, bacteriophages]
-
A.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
B.
researchModel
Indicates that an entity systematically investigates, develops, or analyzes a model as part of a research process.
-
C.
researchMode
Indicates that an entity is engaged in or configured for conducting systematic investigation, experimentation, or study.
-
D.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
E.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46577989081909278965a9844ebad |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:27 a.m.