Triple

T16968386
Position Surface form Disambiguated ID Type / Status
Subject Mikulčice E411601 entity
Predicate numberOfChurchesExcavated P12144 FINISHED
Object at least 10 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: at least 10 | Statement: [Mikulčice, numberOfChurchesExcavated, at least 10]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: numberOfChurchesExcavated
Context triple: [Mikulčice, numberOfChurchesExcavated, at least 10]
  • A. numberOfArchaeologicalSites
    Indicates the total count of archaeological sites associated with a given entity or context.
  • B. hasNumberOfChurches chosen
    Indicates the relationship that specifies how many churches are associated with a given entity.
  • C. hasArchaeologicalExcavationsBy
    Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
  • D. hasParishChurchesIn
    Indicates that an entity possesses or is associated with one or more parish churches located within a specified area or jurisdiction.
  • E. archaeologicalExcavations
    Indicates that archaeological excavations have been carried out on or are associated with the subject, typically involving systematic digging and recovery of material remains.
  • 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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0a6f628819080db47285954729a completed April 18, 2026, 6:42 p.m.
PD Predicate disambiguation batch_69e35d4dff4881909b384e30f2d36bff completed April 18, 2026, 10:30 a.m.
Created at: April 10, 2026, 5:31 a.m.