Triple

T3300320
Position Surface form Disambiguated ID Type / Status
Subject Pummerin bell E69313 entity
Predicate originallyCastFrom P47847 FINISHED
Object captured Turkish cannons 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: captured Turkish cannons | Statement: [Pummerin bell, originallyCastFrom, captured Turkish cannons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originallyCastFrom
Context triple: [Pummerin bell, originallyCastFrom, captured Turkish cannons]
  • A. originallyBy
    Indicates that one entity is the original creator, author, or source of another entity.
  • B. originallyRecordedFor
    Indicates that a work or performance was first recorded with the specific purpose of being used, released, or presented in the context of the target entity.
  • C. originallyCoveredBy
    Indicates that something was first protected, reported on, or documented by a particular source, medium, or entity before any others.
  • D. wasOriginally
    Indicates that an entity had a particular state, form, type, or affiliation at an earlier time, which has since changed.
  • E. originallyIn
    Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
  • 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_69ad859e529c8190a404273f53cb487d completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb0a66fcc819093931fe7a6507723 completed March 8, 2026, 5:23 p.m.
PD Predicate disambiguation batch_69ada42407dc81909f60d7a14e1b7934 completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada526764881908e4bd52938d5374d completed March 8, 2026, 4:34 p.m.
Created at: March 8, 2026, 3:11 p.m.