Triple
T8160632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quail Hill |
E190567
|
entity |
| Predicate | recreationFocus |
P80753
|
FINISHED |
| Object | outdoor recreation |
—
|
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: outdoor recreation | Statement: [Quail Hill, recreationFocus, outdoor recreation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recreationFocus Context triple: [Quail Hill, recreationFocus, outdoor recreation]
-
A.
recreationAccessPoint
Indicates a location or facility that serves as an entry or starting point for engaging in recreational activities.
-
B.
recreationSeason
Indicates the time of year or specific season during which a recreational activity, facility, or area is typically used or available.
-
C.
hasRecreationPurpose
chosen
Indicates that something is used or intended to be used for recreational or leisure activities.
-
D.
celebrationFocus
Indicates that the primary subject or emphasis of a celebration is directed toward a particular entity or theme.
-
E.
recreationRegulation
Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455559188190bf95d9d93bb76002 |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.