Triple
T26639441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Si Trail |
E668734
|
entity |
| Predicate | dogsMustBeOnLeash |
P14057
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Little Si Trail, dogsMustBeOnLeash, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dogsMustBeOnLeash Context triple: [Little Si Trail, dogsMustBeOnLeash, yes]
-
A.
cannotBeLeashed
Indicates that one entity is not allowed or not able to be restrained, controlled, or attached using a leash by another entity.
-
B.
usesCaninesFor
Indicates a relationship where an entity employs or relies on its canine teeth for a particular function or activity.
-
C.
petPolicy
chosen
Indicates the rules or conditions governing whether and how pets are allowed in relation to a place, service, or arrangement.
-
D.
groomingRestriction
Indicates that there is a rule or limitation imposed on how grooming or personal care activities may be performed.
-
E.
rideRestriction
Indicates that there is a limitation or rule governing whether, how, or under what conditions one entity may ride or be transported by another.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6162f62b481908fa62a557e1297d8 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:28 a.m.