Triple
T22807224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Hesperia Planning Area |
E564568
|
entity |
| Predicate | mayOverlap |
P1867
|
FINISHED |
| Object | San Bernardino County planning jurisdiction |
—
|
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: San Bernardino County planning jurisdiction | Statement: [City of Hesperia Planning Area, mayOverlap, San Bernardino County planning jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayOverlap Context triple: [City of Hesperia Planning Area, mayOverlap, San Bernardino County planning jurisdiction]
-
A.
overlapsWith
chosen
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
B.
mayCross
Indicates that one entity is permitted or allowed to cross or pass over another entity or boundary.
-
C.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
D.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
E.
mayNotFit
Indicates that one entity is unlikely or not expected to be suitable in size, capacity, or compatibility to be placed into, combined with, or used within another entity or context.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5d41dc819081912d9e29828bfb |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.