Triple
T21165383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Póvoa de Varzim |
E521546
|
entity |
| Predicate | grantedMunicipalCharterIn |
P58650
|
FINISHED |
| Object | 1308 |
—
|
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: 1308 | Statement: [Póvoa de Varzim, grantedMunicipalCharterIn, 1308]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedMunicipalCharterIn Context triple: [Póvoa de Varzim, grantedMunicipalCharterIn, 1308]
-
A.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
B.
hadBoroughCharter
chosen
Indicates that an entity was formally granted a borough charter, conferring it the legal status and privileges of a borough.
-
C.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity or domain.
-
D.
governedByCharterFrom
Indicates that an entity operates under the authority, rules, or framework established by a specific charter issued by another entity.
-
E.
hasCharter
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
- 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7270e15bc81908d609198e573040e |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.