Triple
T37482168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mudi |
E931437
|
entity |
| Predicate | recognizedAsDistinctBreed |
P147903
|
FINISHED |
| Object | 20th century in Hungary |
—
|
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: 20th century in Hungary | Statement: [Mudi, recognizedAsDistinctBreed, 20th century in Hungary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsDistinctBreed Context triple: [Mudi, recognizedAsDistinctBreed, 20th century in Hungary]
-
A.
recognizedAsSeparateBreedFrom
Indicates that one animal population or type is officially acknowledged as a distinct breed, separate from another.
-
B.
isRecognizedAsBreed
chosen
Indicates that an entity is officially acknowledged or accepted as a distinct breed within a particular classification or standard.
-
C.
hasTypicalBreed
Indicates that an entity (such as an animal or pet) is associated with a breed that is considered standard or characteristic for its kind.
-
D.
sameBreedAs
Indicates that two entities belong to the same breed or variety within a species.
-
E.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: May 3, 2026, 4:17 p.m.