Triple
T31998286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dublin Port Tunnel |
E817051
|
entity |
| Predicate | openedToHGVs |
P190066
|
FINISHED |
| Object | 2006-12-20 |
—
|
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: 2006-12-20 | Statement: [Dublin Port Tunnel, openedToHGVs, 2006-12-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToHGVs Context triple: [Dublin Port Tunnel, openedToHGVs, 2006-12-20]
-
A.
clinicalSignificanceOfVariants
Indicates the assessed clinical importance or impact that specific genetic variants have in a medical or diagnostic context.
-
B.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
C.
hasGene
Indicates that an entity possesses or contains a specific gene as part of its genetic makeup.
-
D.
geneticFindings
Indicates that there is information describing observed genetic variants, mutations, or other genomic characteristics identified in an entity.
-
E.
hasHGNCID
Indicates that an entity (typically a gene) is associated with a specific identifier assigned by the HUGO Gene Nomenclature Committee (HGNC).
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 1, 2026, 12:14 a.m.