Triple

T21793563
Position Surface form Disambiguated ID Type / Status
Subject Albanopolis E538035 entity
Predicate culturalAttributionStatus P145669 FINISHED
Object disputed 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: disputed | Statement: [Albanopolis, culturalAttributionStatus, disputed]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: culturalAttributionStatus
Context triple: [Albanopolis, culturalAttributionStatus, disputed]
  • A. cultureAttributedTo
    Indicates that a particular cultural style, tradition, or influence is ascribed to or associated with a specific source, group, or origin.
  • B. cultureStatus
    Indicates the current condition or state of a culture (e.g., biological, social, or organizational) in relation to its development, viability, or activity.
  • C. hasCulturalProtection
    Indicates that an entity is subject to legal or formal measures intended to preserve and safeguard its cultural value or heritage.
  • D. architectAttributionStatus
    Indicates the degree of certainty or status regarding who is credited as the architect for a given work or project.
  • E. hasCulturalInstitutionStatus
    Indicates that an entity holds an official designation or recognition as a cultural institution.
  • 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_69e0c4733f4081909a86622e7e6d15d2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f06221d1f4819089bb113d808d79c2 completed April 28, 2026, 7:30 a.m.
PD Predicate disambiguation batch_69e6be751ce881909badced245ef76c7 completed April 21, 2026, 12:01 a.m.
PDg Predicate description generation batch_69e6c3a2898881909748935cf92f898c completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 6:52 p.m.