Triple

T33329535
Position Surface form Disambiguated ID Type / Status
Subject 仁徳天皇 E853363 entity
Predicate 陵墓管理者 P39127 FINISHED
Object 宮内庁 NE NERFINISHED

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: 宮内庁 | Statement: [仁徳天皇, 陵墓管理者, 宮内庁]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 陵墓管理者
Context triple: [仁徳天皇, 陵墓管理者, 宮内庁]
  • A. necropolisRole chosen
    Indicates that an entity has a specific functional or social role in relation to a necropolis (a large cemetery or burial ground).
  • B. managesOneOfLargestCemeteriesIn
    Indicates that an entity is responsible for operating or overseeing one of the largest cemeteries located in a specified place.
  • C. cemeteryOwner
    Indicates that one entity owns, controls, or holds legal responsibility for a cemetery associated with another entity.
  • D. belongsToNecropolis
    Indicates that something is part of, contained within, or associated with a particular necropolis.
  • E. managesOneOfOldestCemeteriesIn
    Indicates that an entity is responsible for overseeing or administering one of the oldest cemeteries located in a specified place.
  • 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_69f34969614c81909cd99661b0902533 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
Created at: May 1, 2026, 1:34 a.m.