Triple
T18604918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of the Popes |
E454715
|
entity |
| Predicate | hasRelatedTheme |
P20616
|
FINISHED |
| Object | medieval church politics |
—
|
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: medieval church politics | Statement: [City of the Popes, hasRelatedTheme, medieval church politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedTheme Context triple: [City of the Popes, hasRelatedTheme, medieval church politics]
-
A.
hasThemeConnection
chosen
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
B.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
C.
hasThematicOrigin
Indicates that something originates from, or is thematically derived from, a particular source, subject, or theme.
-
D.
associatedThemeElements
Indicates a relationship where certain elements are linked to, or grouped under, a particular theme as its related components.
-
E.
usesThemeFrom
Indicates that one work incorporates, references, or is based on the thematic material of another work.
- 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.