Triple

T6213728
Position Surface form Disambiguated ID Type / Status
Subject Monte Toro E138931 entity
Predicate hasMonasteryBuildings P20652 FINISHED
Object yes 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: yes | Statement: [Monte Toro, hasMonasteryBuildings, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMonasteryBuildings
Context triple: [Monte Toro, hasMonasteryBuildings, yes]
  • A. containsMonastery chosen
    Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
  • B. hasClericalStructure
    Indicates that an entity possesses an organized clerical or administrative hierarchy or framework.
  • C. hasNearbyMonastery
    Indicates that one entity is located close to or in the vicinity of a monastery.
  • D. hasTempleOf
    Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
  • E. hasSubTemple
    Indicates that one temple includes or contains another temple as a subordinate or component temple within its structure or organization.
  • 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_69c008ada364819096c9e92c74d639b5 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0629fd3c08190a121097c188417c4 completed March 22, 2026, 9:44 p.m.
PD Predicate disambiguation batch_69c055fdea3c81908f5d910f0d36234a completed March 22, 2026, 8:50 p.m.
Created at: March 22, 2026, 4:21 p.m.