Triple
T3872105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caenorhabditis elegans |
E92409
|
entity |
| Predicate | referenceStrain |
P33736
|
FINISHED |
| Object | N2 Bristol |
—
|
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: N2 Bristol | Statement: [Caenorhabditis elegans, referenceStrain, N2 Bristol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceStrain Context triple: [Caenorhabditis elegans, referenceStrain, N2 Bristol]
-
A.
standardReference
chosen
Indicates that one entity serves as the authoritative or canonical reference or benchmark for interpreting, validating, or comparing another entity.
-
B.
relatedSpeciesOrVariant
Indicates that one species or biological variant is taxonomically or genetically related to another.
-
C.
primaryReference
Indicates that one entity serves as the main or authoritative source of information or citation for another entity.
-
D.
bacteriumIdentifiedIn
Indicates that a specific bacterium has been detected, recognized, or confirmed as present in a particular sample, environment, or host.
-
E.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec5691148190b469af0bee9154db |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.