Triple
T29753085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad River Glen |
E752953
|
entity |
| Predicate | groomingPolicy |
P112804
|
FINISHED |
| Object | selective grooming |
—
|
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: selective grooming | Statement: [Mad River Glen, groomingPolicy, selective grooming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groomingPolicy Context triple: [Mad River Glen, groomingPolicy, selective grooming]
-
A.
governingPolicy
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
-
B.
groomingRestriction
chosen
Indicates that there is a rule or limitation imposed on how grooming or personal care activities may be performed.
-
C.
preservationPolicy
Indicates the rules or strategy governing how something is maintained, protected, and retained over time.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
gradingPolicy
Indicates the rules or criteria that determine how performance or work is evaluated and assigned grades.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673c8c00881908596a9e9fca49436 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:55 p.m.