Triple
T4874286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contra Loma Regional Park |
E109162
|
entity |
| Predicate | waterRecreation |
P46319
|
FINISHED |
| Object | non-motorized boating |
—
|
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: non-motorized boating | Statement: [Contra Loma Regional Park, waterRecreation, non-motorized boating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterRecreation Context triple: [Contra Loma Regional Park, waterRecreation, non-motorized boating]
-
A.
waterSport
Indicates participation in or association with a sport or recreational activity that takes place on or in water.
-
B.
canoeingVenue
Indicates that a location serves as a site or facility where canoeing activities take place.
-
C.
boatingAllowed
chosen
Indicates that operating or using boats is permitted in the specified area or context.
-
D.
tookOnWater
Indicates that an entity began to fill or absorb water, typically in an unintended or problematic way (e.g., a vessel leaking or flooding).
-
E.
waterbodyUsedFor
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.