Triple
T36275893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utility Group |
E892808
|
entity |
| Predicate | includesBreedsDevelopedFor |
P191311
|
FINISHED |
| Object | guarding |
—
|
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: guarding | Statement: [Utility Group, includesBreedsDevelopedFor, guarding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesBreedsDevelopedFor Context triple: [Utility Group, includesBreedsDevelopedFor, guarding]
-
A.
breedsIn
Indicates that an organism reproduces or carries out its breeding activities within a specified environment, habitat, or location.
-
B.
wasBredFor
chosen
Indicates that one entity was selectively bred or developed for a particular purpose, function, or use associated with another entity.
-
C.
breedsFrom
Indicates that one organism or entity is produced, derived, or propagated from another through breeding or reproductive processes.
-
D.
breed
Indicates that an organism reproduces to generate offspring, typically with another organism of the same species.
-
E.
associatedAnimalBreed
Indicates that there is a relationship linking an entity to a specific breed of animal with which it is connected or identified.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.