Triple
T12978024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Altos Hills |
E321579
|
entity |
| Predicate | isZonedFor |
P76534
|
FINISHED |
| Object | low-density housing |
—
|
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: low-density housing | Statement: [Los Altos Hills, isZonedFor, low-density housing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isZonedFor Context triple: [Los Altos Hills, isZonedFor, low-density housing]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
zonedTo
chosen
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
C.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
D.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
-
E.
supportsZoneSystem
Indicates that one entity provides compatibility with or implementation of a specific zone-based system used by 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:38 p.m.