Triple
T22382790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajima strain of Japanese Black |
E553316
|
entity |
| Predicate | geneticLineageOf |
P115355
|
FINISHED |
| Object | Kobe beef cattle |
—
|
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: Kobe beef cattle | Statement: [Tajima strain of Japanese Black, geneticLineageOf, Kobe beef cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticLineageOf Context triple: [Tajima strain of Japanese Black, geneticLineageOf, Kobe beef cattle]
-
A.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
B.
sourceOfLineageFor
chosen
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
-
C.
heritageLine
Indicates that one entity is a historical or traditional predecessor, lineage, or source from which the other entity derives or continues.
-
D.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
E.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582cce608190b5324b30f349a3ff |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.