Triple
T28499749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yunnan ham |
E721200
|
entity |
| Predicate | typicalAnimalBreed |
P193935
|
FINISHED |
| Object | local Yunnan pig breeds |
—
|
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: local Yunnan pig breeds | Statement: [Yunnan ham, typicalAnimalBreed, local Yunnan pig breeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAnimalBreed Context triple: [Yunnan ham, typicalAnimalBreed, local Yunnan pig breeds]
-
A.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
B.
hasTypicalBreed
chosen
Indicates that an entity (such as an animal or pet) is associated with a breed that is considered standard or characteristic for its kind.
-
C.
animalTypeFeatured
Indicates that a particular type or category of animal is highlighted or prominently showcased in a given context.
-
D.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
E.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00af6b3a948190a92813c13384c304 |
completed | May 10, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_6a00aec35610819085dd5137715a4228 |
completed | May 10, 2026, 4:13 p.m. |
Created at: April 28, 2026, 3:06 a.m.