Triple
T25133106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charolais-Brionnais area |
E629580
|
entity |
| Predicate | notableBreed |
P41121
|
FINISHED |
| Object | Charolais cattle |
—
|
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: Charolais cattle | Statement: [Charolais-Brionnais area, notableBreed, Charolais cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBreed Context triple: [Charolais-Brionnais area, notableBreed, Charolais cattle]
-
A.
notableDog
Indicates that the subject is a dog recognized for its significance, fame, or special distinction.
-
B.
associatedAnimalBreed
chosen
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
C.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
D.
isHeritageBreed
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
E.
isRecognizedAsBreed
Indicates that an entity is officially acknowledged or accepted as a distinct breed within a particular classification or standard.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 18, 2026, 6:28 a.m.