Triple
T26878064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajima beef |
E676808
|
entity |
| Predicate | geneticSourceOf |
P87422
|
FINISHED |
| Object | Yonezawa beef |
—
|
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: Yonezawa beef | Statement: [Tajima beef, geneticSourceOf, Yonezawa beef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticSourceOf Context triple: [Tajima beef, geneticSourceOf, Yonezawa beef]
-
A.
geneticOrigin
chosen
Indicates that one entity is the source or contributor of another entity’s genetic material or hereditary traits.
-
B.
geneticInfluence
Indicates that one entity affects or contributes to the genetic traits, characteristics, or heredity of another entity.
-
C.
geneticallyLinkedTo
Indicates a relationship where two entities share a genetic connection, such as common ancestry, shared genes, or hereditary association.
-
D.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
E.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 5:37 a.m.