Triple
T14597178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | São José (Ponta Delgada) |
E342599
|
entity |
| Predicate | sharesMunicipalityWith |
P87345
|
FINISHED |
| Object | other parishes of Ponta Delgada |
—
|
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: other parishes of Ponta Delgada | Statement: [São José (Ponta Delgada), sharesMunicipalityWith, other parishes of Ponta Delgada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMunicipalityWith Context triple: [São José (Ponta Delgada), sharesMunicipalityWith, other parishes of Ponta Delgada]
-
A.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
B.
sharesProvinceWith
Indicates that two entities are located within, or associated with, the same administrative province.
-
C.
sharesCountyWith
Indicates that two entities are located within the same county jurisdiction.
-
D.
sharesLocalGovernmentWith
chosen
Indicates that two entities are administered by the same local governmental authority or jurisdiction.
-
E.
neighbouringMunicipality
Indicates that one municipality directly borders and is adjacent to another municipality.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb436d92881908fdf9267568feee2 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.