Triple
T9709057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spangled Orpington |
E234973
|
entity |
| Predicate | belongsToBreedFamily |
P4276
|
FINISHED |
| Object | English class chickens |
—
|
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: English class chickens | Statement: [Spangled Orpington, belongsToBreedFamily, English class chickens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToBreedFamily Context triple: [Spangled Orpington, belongsToBreedFamily, English class chickens]
-
A.
belongsToBreedGroup
Indicates that an animal is classified as a member of a specific breed group.
-
B.
breedingFamily
Indicates that one entity belongs to or is part of the family group used for breeding or reproduction with the other entity.
-
C.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
-
D.
belongsToFamily
chosen
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
E.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.