Triple
T25137526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fernando, California |
E629700
|
entity |
| Predicate | hasOwnMunicipalGovernment |
P86694
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [San Fernando, California, hasOwnMunicipalGovernment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnMunicipalGovernment Context triple: [San Fernando, California, hasOwnMunicipalGovernment, true]
-
A.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
B.
hasLocalSelfGovernment
chosen
Indicates that an entity possesses its own local governing authority with decision-making powers over local affairs.
-
C.
hasLocalGovernmentSystem
Indicates that an entity possesses or operates under a particular system or structure of local government.
-
D.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
-
E.
hasLocalGovernmentBody
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46600ae608190ae5e662fd4a7e5a5 |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.