Triple

T1987074
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Trento E43165 entity
Predicate isMetropolitanSee P20454 FINISHED
Object true 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: true | Statement: [Diocese of Trento, isMetropolitanSee, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMetropolitanSee
Context triple: [Diocese of Trento, isMetropolitanSee, true]
  • A. metropolitanSee
    Indicates a relationship where one metropolitan area views, oversees, or conceptually regards another place, entity, or aspect within its sphere of influence.
  • B. hasMetropolitanSee chosen
    Indicates that one ecclesiastical jurisdiction serves as the metropolitan (primary or overseeing) see in relation to another church territory.
  • C. hasMetropolitan
    Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
  • D. isMetropolitanCoreOf
    Indicates that one area functions as the central, most urbanized core within a larger metropolitan region or system.
  • E. isMetropolitanCity
    Indicates that a city qualifies as a major urban center, typically characterized by large population, extensive infrastructure, and significant economic, cultural, or administrative importance.
  • 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_69a88713ddc88190a969715658ebe7a8 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb96f932881908bebfc4176fda7c0 completed March 7, 2026, 5:36 a.m.
PD Predicate disambiguation batch_69abb798d288819083132cf14605bd02 completed March 7, 2026, 5:28 a.m.
Created at: March 4, 2026, 7:37 p.m.