Triple
T5877857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobe beef |
E130669
|
entity |
| Predicate | isOftenMisusedAsTermFor |
P46176
|
FINISHED |
| Object | high-quality beef in general |
—
|
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: high-quality beef in general | Statement: [Kobe beef, isOftenMisusedAsTermFor, high-quality beef in general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenMisusedAsTermFor Context triple: [Kobe beef, isOftenMisusedAsTermFor, high-quality beef in general]
-
A.
termAlsoUsedFor
chosen
Indicates that one term is also used to refer to the same or closely related concept as another term.
-
B.
usedTerm
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
C.
notPreferredTermFor
Indicates that one term is a non-preferred or deprecated label that should be replaced by another, preferred term in a controlled vocabulary or terminology system.
-
D.
oftenConfusedWith
Indicates that one entity is frequently mistaken for or thought to be another due to similarity or ambiguity.
-
E.
isFrequentlyDescribedAs
Indicates that something is often characterized or referred to using a particular description or set of attributes.
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.