Triple
T196341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Park |
E3826
|
entity |
| Predicate | regulatesActivity |
P3020
|
FINISHED |
| Object | skateboarding (periodically restricted) |
—
|
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: skateboarding (periodically restricted) | Statement: [Love Park, regulatesActivity, skateboarding (periodically restricted)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesActivity Context triple: [Love Park, regulatesActivity, skateboarding (periodically restricted)]
-
A.
regulatesUse
chosen
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
B.
supportsActivity
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
C.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
D.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
E.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25983b49c819080f7e161904c53da |
completed | Feb. 28, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.