Triple
T2933575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Harriet |
E79210
|
entity |
| Predicate | hasUsePolicy |
P10265
|
FINISHED |
| Object | public park hours apply |
—
|
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: public park hours apply | Statement: [Lake Harriet, hasUsePolicy, public park hours apply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsePolicy Context triple: [Lake Harriet, hasUsePolicy, public park hours apply]
-
A.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
-
B.
hasVisitorPolicy
chosen
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
-
C.
usesMaterialsPolicy
Indicates that an entity follows, applies, or is governed by a specified policy regarding the use of materials.
-
D.
usesPolicyModel
Indicates that one entity applies, relies on, or operates according to a particular policy model.
-
E.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983b65f881909b8b7d3dc5c224fd |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.