Triple
T33057728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogport Dog Park |
E845886
|
entity |
| Predicate | leashPolicy |
P11196
|
FINISHED |
| Object | off-leash within fenced areas |
—
|
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: off-leash within fenced areas | Statement: [Dogport Dog Park, leashPolicy, off-leash within fenced areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leashPolicy Context triple: [Dogport Dog Park, leashPolicy, off-leash within fenced areas]
-
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.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
C.
locationPolicy
chosen
Indicates a rule or constraint governing where an entity is allowed, required, or restricted to be located.
-
D.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
-
E.
trialPolicy
Indicates that an entity offers or is subject to a trial period, specifying the conditions under which the trial can be used or accessed.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.