Triple
T36463765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takifugu rubripes |
E898369
|
entity |
| Predicate | hasGenomeProject |
P195746
|
FINISHED |
| Object | Fugu genome project |
—
|
NE NERFINISHED |
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: Fugu genome project | Statement: [Takifugu rubripes, hasGenomeProject, Fugu genome project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenomeProject Context triple: [Takifugu rubripes, hasGenomeProject, Fugu genome project]
-
A.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
B.
haveGenomeFeatures
Indicates that an entity possesses or is associated with specific genomic features (such as genes, regulatory elements, or sequence annotations).
-
C.
hasGenomeType
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
D.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
-
E.
genomeSequencedFor
Indicates that the complete or partial genetic sequence of one entity has been determined specifically for or in relation to another entity.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: May 3, 2026, 4:10 p.m.