Triple
T21684023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buena Vista Park |
E535183
|
entity |
| Predicate | dogOffLeashPolicy |
P14057
|
FINISHED |
| Object | designated off-leash area |
—
|
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: designated off-leash area | Statement: [Buena Vista Park, dogOffLeashPolicy, designated off-leash area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dogOffLeashPolicy Context triple: [Buena Vista Park, dogOffLeashPolicy, designated off-leash area]
-
A.
petPolicy
chosen
Indicates the rules or conditions governing whether and how pets are allowed in relation to a place, service, or arrangement.
-
B.
cannotBeLeashed
Indicates that one entity is not allowed or not able to be restrained, controlled, or attached using a leash by another entity.
-
C.
usesCaninesFor
Indicates a relationship where an entity employs or relies on its canine teeth for a particular function or activity.
-
D.
walkingPolicy
Indicates the rules or guidelines that govern how walking is allowed, managed, or restricted in a given context.
-
E.
cityParkStatus
Indicates the current operational or accessibility status of a city park in relation to its governing jurisdiction or management.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96c943888190acd783ce8677087c |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:43 p.m.