Triple
T33315769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encino Golf Course |
E853009
|
entity |
| Predicate | walkingOnlyAreas |
P6741
|
FINISHED |
| Object | golf course fairways and greens |
—
|
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: golf course fairways and greens | Statement: [Encino Golf Course, walkingOnlyAreas, golf course fairways and greens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkingOnlyAreas Context triple: [Encino Golf Course, walkingOnlyAreas, golf course fairways and greens]
-
A.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
-
B.
pedestrianOnly
chosen
Indicates that a path, area, or route is designated exclusively for pedestrians and prohibits vehicle access.
-
C.
wirdBegangenIn
Indicates that an action, event, or offense is committed or takes place within a specified location or context.
-
D.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
-
E.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.