Triple
T25029237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish Terrier |
E626791
|
entity |
| Predicate | groomingRequirement |
P40686
|
FINISHED |
| Object | frequent brushing |
—
|
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: frequent brushing | Statement: [Scottish Terrier, groomingRequirement, frequent brushing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groomingRequirement Context triple: [Scottish Terrier, groomingRequirement, frequent brushing]
-
A.
groomingNeeds
chosen
Indicates the level, type, or frequency of grooming care required for an entity.
-
B.
groomingRestriction
Indicates that there is a rule or limitation imposed on how grooming or personal care activities may be performed.
-
C.
hasGrooming
Indicates that one entity performs grooming behavior on, or receives grooming from, another entity.
-
D.
hasFurType
Indicates that an entity possesses a specific kind or texture of fur.
-
E.
hasBreedStandardRestriction
Indicates that there is a rule or limitation defined in a breed standard that restricts how the entity may be bred, shown, or classified.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:07 a.m.