Triple
T34030058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratovecchio |
E872617
|
entity |
| Predicate | newMunicipalityName |
P178160
|
FINISHED |
| Object | Pratovecchio Stia |
—
|
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: Pratovecchio Stia | Statement: [Pratovecchio, newMunicipalityName, Pratovecchio Stia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newMunicipalityName Context triple: [Pratovecchio, newMunicipalityName, Pratovecchio Stia]
-
A.
municipalityName
Indicates the official name assigned to a municipality.
-
B.
previousMunicipalityNameVariant
Indicates that an entity had a different municipality name in the past, specifying a former variant of its municipal designation.
-
C.
hasNameInMunicipality
Indicates that an entity is known by a particular name within the context or jurisdiction of a specific municipality.
-
D.
proposedStateName
Indicates that one entity has suggested or put forward a particular name to be used as the state name for another entity.
-
E.
formedMunicipalityWith
Indicates that two or more entities combined or were merged to create a single municipality.
- F. None of above. chosen
Provenance (4 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:51 a.m.