Triple

T16809450
Position Surface form Disambiguated ID Type / Status
Subject Inch Abbey E408568 entity
Predicate hasRuinType P32402 FINISHED
Object church 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: church | Statement: [Inch Abbey, hasRuinType, church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRuinType
Context triple: [Inch Abbey, hasRuinType, church]
  • A. hasRuin chosen
    Indicates that one entity possesses, contains, or is associated with a ruin or ruined structure.
  • B. hasRelicType
    Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
  • C. hasTypeOfDamage
    Indicates that an entity experiences or exhibits a specific kind or category of damage.
  • D. hasHullType
    Indicates that an entity possesses or is characterized by a specific type or form of hull.
  • E. hasSkullType
    Indicates that an entity possesses or is characterized by a specific type or classification of skull.
  • 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2ceab608190a9c8cd339ddbea0a completed April 18, 2026, 4:35 p.m.
PD Predicate disambiguation batch_69e32b814b188190aee525f8779203cd completed April 18, 2026, 6:58 a.m.
Created at: April 10, 2026, 5:23 a.m.