Triple
T26878067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajima beef |
E676808
|
entity |
| Predicate | cattleBreedStrain |
P54029
|
FINISHED |
| Object | Tajima strain |
—
|
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: Tajima strain | Statement: [Tajima beef, cattleBreedStrain, Tajima strain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cattleBreedStrain Context triple: [Tajima beef, cattleBreedStrain, Tajima strain]
-
A.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
B.
typeOfLivestock
Indicates the specific kind or category of livestock associated with or involved in a given context or entity.
-
C.
targetStrain
chosen
Indicates that one entity is the specific strain (e.g., genetic, microbial, or biological variant) that is the focus or objective of another entity’s action, study, or effect.
-
D.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
E.
wasBredIn
Indicates that an organism or animal was raised or produced through breeding in a particular place or environment.
- 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_69f61f1a5f9881908a7d4ff6e5f783ca |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:37 a.m.