Triple
T16318545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N2 Bristol |
E396232
|
entity |
| Predicate | referenceGenomeFor |
P35224
|
FINISHED |
| Object | Caenorhabditis elegans genome |
—
|
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: Caenorhabditis elegans genome | Statement: [N2 Bristol, referenceGenomeFor, Caenorhabditis elegans genome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceGenomeFor Context triple: [N2 Bristol, referenceGenomeFor, Caenorhabditis elegans genome]
-
A.
genomeSource
chosen
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
B.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
C.
EnsemblGeneID
Indicates a relationship that assigns or associates a biological entity (such as a gene) with its unique Ensembl gene identifier.
-
D.
NCBIGeneID
Indicates a relationship that assigns or links an entity to its unique gene identifier as defined in the NCBI Gene database.
-
E.
genomeSize
Indicates the total amount of genetic material (e.g., in base pairs) contained in an organism’s genome.
- 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.