Triple
T30370896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exmoor pony |
E772545
|
entity |
| Predicate | isAncientBreed |
P82277
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Exmoor pony, isAncientBreed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAncientBreed Context triple: [Exmoor pony, isAncientBreed, true]
-
A.
isHeritageBreed
chosen
Indicates that an animal breed belongs to a traditional, historically established lineage recognized for its cultural, genetic, or agricultural heritage.
-
B.
isRecognizedAsBreed
Indicates that an entity is officially acknowledged or accepted as a distinct breed within a particular classification or standard.
-
C.
hasTraditionalAnimalBreed
Indicates that an entity is associated with or possesses an animal that belongs to a recognized traditional breed.
-
D.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
E.
recognizedAsSeparateBreedFrom
Indicates that one animal population or type is officially acknowledged as a distinct breed, separate from another.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682836d308190b22a0efc893e7a45 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.