Triple
T18334737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Benedict |
E439240
|
entity |
| Predicate | geneticallyEngineered |
P126444
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Julius Benedict, geneticallyEngineered, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticallyEngineered Context triple: [Julius Benedict, geneticallyEngineered, true]
-
A.
geneticallyManipulatedBy
chosen
Indicates that an entity’s genetic material has been altered or modified as a result of actions performed by another specified agent or process.
-
B.
geneticElement
Indicates that one entity is a genetic element (such as a gene, sequence, or structural unit of genetic material) associated with or characterized by the other entity.
-
C.
transgenesisMethod
Indicates the method or technique used to introduce foreign genetic material into an organism’s genome.
-
D.
geneticallyIdenticalTo
Indicates that two entities share the same genetic makeup, with no differences in their DNA sequence.
-
E.
biologicalOrigin
Indicates that one entity originates from, is derived from, or is produced by a biological source or organism in relation to another entity.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecc91148190aa820fcd466009ce |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.