Triple
T23755126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ecclesiastical Region of Emilia-Romagna |
E587086
|
entity |
| Predicate | civilRegionCorrespondence |
P153568
|
FINISHED |
| Object | Emilia-Romagna |
—
|
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: Emilia-Romagna | Statement: [Ecclesiastical Region of Emilia-Romagna, civilRegionCorrespondence, Emilia-Romagna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilRegionCorrespondence Context triple: [Ecclesiastical Region of Emilia-Romagna, civilRegionCorrespondence, Emilia-Romagna]
-
A.
governmentRegionFor
Indicates that a government entity has jurisdiction over or is associated with a specific geographic region.
-
B.
concernsRegion
Indicates that something is about, relates to, or is specifically associated with a particular geographic or administrative region.
-
C.
registrationRegion
Indicates the geographic or administrative region in which an entity is officially registered.
-
D.
hasPostalAddressRegion
Indicates the region component (such as state, province, or area) associated with an entity’s postal address.
-
E.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdab86108190becd7f27650082cc |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:14 p.m.