Triple
T25091210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Rural District |
E628460
|
entity |
| Predicate | hadLocalGovernmentFunction |
P157632
|
FINISHED |
| Object | local planning |
—
|
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: local planning | Statement: [Richmond Rural District, hadLocalGovernmentFunction, local planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadLocalGovernmentFunction Context triple: [Richmond Rural District, hadLocalGovernmentFunction, local planning]
-
A.
hadLocalGovernmentFunction
chosen
Indicates that an entity previously exercised responsibilities or powers as a local governing authority within a specific area or jurisdiction.
-
B.
hasLocalGovernmentOffice
Indicates that a local government office is present or established within a specified location or jurisdiction.
-
C.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
D.
hasLocalGovernmentHistory
Indicates that an entity has a documented history or record of its local governmental structure, activities, or developments.
-
E.
hasLocalSelfGovernment
Indicates that an entity possesses its own local governing authority with decision-making powers over local affairs.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 6:24 a.m.