Triple
T9341384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indominus rex |
E224769
|
entity |
| Predicate | geneticSources |
P35224
|
FINISHED |
| Object | Tyrannosaurus rex DNA |
—
|
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: Tyrannosaurus rex DNA | Statement: [Indominus rex, geneticSources, Tyrannosaurus rex DNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticSources Context triple: [Indominus rex, geneticSources, Tyrannosaurus rex DNA]
-
A.
genomeSource
chosen
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
B.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
C.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
D.
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.
-
E.
geneticAffinity
Indicates a relationship where entities share a notable degree of genetic similarity or relatedness.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bafa9108190889397614756020d |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.