Triple
T18036803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laguiole cheese |
E431527
|
entity |
| Predicate | traditionalBreedUsed |
P41121
|
FINISHED |
| Object | Aubrac 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: Aubrac cattle | Statement: [Laguiole cheese, traditionalBreedUsed, Aubrac cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalBreedUsed Context triple: [Laguiole cheese, traditionalBreedUsed, Aubrac cattle]
-
A.
hasTraditionalAnimalBreed
Indicates that an entity is associated with or possesses an animal that belongs to a recognized traditional breed.
-
B.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
C.
associatedAnimalBreed
chosen
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
D.
bredWith
Indicates that one entity has been used to reproduce or mate with another entity, typically for the purpose of producing offspring.
-
E.
madeFromBreed
Indicates that something is produced or derived using a particular breed as its source or primary constituent.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4be3a80508190b667c3f6d14f5c84 |
completed | April 19, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.