Triple
T30856482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of The Blue Mountains |
E785934
|
entity |
| Predicate | hasMunicipalOfficeIn |
P59022
|
FINISHED |
| Object | Thornbury |
—
|
NE NERFINISHED |
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: Thornbury | Statement: [Town of The Blue Mountains, hasMunicipalOfficeIn, Thornbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalOfficeIn Context triple: [Town of The Blue Mountains, hasMunicipalOfficeIn, Thornbury]
-
A.
hasLocalGovernmentOffice
chosen
Indicates that a local government office is present or established within a specified location or jurisdiction.
-
B.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
C.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
D.
hasMunicipalSeatFunction
Indicates that an entity serves as the administrative or municipal seat (central governing location) for a municipality.
-
E.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 29, 2026, 8:46 p.m.