Triple
T30721989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tetrapolitan Confession |
E782176
|
entity |
| Predicate | cityGroupType |
P170070
|
FINISHED |
| Object | imperial cities of the Holy Roman Empire |
—
|
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: imperial cities of the Holy Roman Empire | Statement: [Tetrapolitan Confession, cityGroupType, imperial cities of the Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityGroupType Context triple: [Tetrapolitan Confession, cityGroupType, imperial cities of the Holy Roman Empire]
-
A.
cityTypeLocation
Indicates that a location is classified as a specific type of city (e.g., capital, metropolitan, coastal).
-
B.
urbanAreaType
Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
-
C.
cityCluster
Indicates a grouping relationship where multiple cities are associated together as part of the same cluster or urban agglomeration.
-
D.
cityDistrictType
Indicates the type or classification of a city district within an urban or administrative structure.
-
E.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5a08648190af6e1d9a99876410 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:36 p.m.