Triple
T25316325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burlingame, California |
E634753
|
entity |
| Predicate | hasTreeOrdinance |
P16838
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Burlingame, California, hasTreeOrdinance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreeOrdinance Context triple: [Burlingame, California, hasTreeOrdinance, yes]
-
A.
hasLocalOrdinances
chosen
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
B.
recognizedAsOrdinanceBy
Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
-
C.
hasTrees
Indicates that something possesses or contains one or more trees.
-
D.
requiresOrdinance
Indicates that one entity can only be established, changed, or carried out if a formal ordinance is enacted or in place.
-
E.
hasTreeCanopyProtection
Indicates that an entity is subject to rules or measures that preserve, limit removal of, or otherwise protect the tree canopy associated with it.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 1:28 p.m.