Triple
T18604910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of the Popes |
E454715
|
entity |
| Predicate | refersToSettlementType |
P26700
|
FINISHED |
| Object | city |
—
|
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: city | Statement: [City of the Popes, refersToSettlementType, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToSettlementType Context triple: [City of the Popes, refersToSettlementType, city]
-
A.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
B.
typeOfSettlement
chosen
Indicates the specific category or classification of a settlement (e.g., city, town, village) that characterizes what kind of settlement it is.
-
C.
governsSettlementType
Indicates that an authority or administrative body exercises governing control over a particular type or category of settlement.
-
D.
isInSettlementType
Indicates that one entity is located within or classified as belonging to a particular type of settlement (such as a city, town, or village).
-
E.
connectsSettlementType
Indicates that there is a relationship linking a settlement to its specific type or classification (e.g., village, town, city).
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e547535b8c8190ab5a8a92f15f2bcb |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.