Triple
T19323152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyote Valley |
E483276
|
entity |
| Predicate | zonedHistoricallyFor |
P135611
|
FINISHED |
| Object | urban reserve (parts) |
—
|
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: urban reserve (parts) | Statement: [Coyote Valley, zonedHistoricallyFor, urban reserve (parts)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zonedHistoricallyFor Context triple: [Coyote Valley, zonedHistoricallyFor, urban reserve (parts)]
-
A.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
B.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
-
C.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
D.
historicallyAttendedBy
Indicates that an entity has been attended by another entity at some point in the past, rather than in the present.
-
E.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
- F. None of above. chosen
Provenance (4 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8a07508190a2e5f8972d1efba0 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4e4709d4481908c280cdd2ac18977 |
completed | April 19, 2026, 2:19 p.m. |
Created at: April 10, 2026, 1:32 p.m.