Triple

T36357494
Position Surface form Disambiguated ID Type / Status
Subject Kōshaku E895384 entity
Predicate rankInKazoku P85550 FINISHED
Object third rank 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: third rank | Statement: [Kōshaku, rankInKazoku, third rank]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankInKazoku
Context triple: [Kōshaku, rankInKazoku, third rank]
  • A. rankWithinKazoku chosen
    Indicates the hierarchical position or status an individual holds within the Kazoku (Japanese peerage) nobility system.
  • B. familyRank
    Indicates the hierarchical position or status an entity holds within a family or kinship structure.
  • C. rankRelativeToDaijō-daijin
    Indicates the relative hierarchical rank or status of an entity in comparison to the position of Daijō-daijin (Chancellor of the Realm).
  • D. rankWithinJapan
    Indicates the relative position or standing of something when compared only among counterparts within Japan.
  • E. rankInJapaneseOrders
    Indicates the position or level an entity holds within the hierarchy of Japanese orders, decorations, or honors.
  • 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_69f76e5044248190b390d8887dc03254 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fcc7338120819081cb46547d60f2cb completed May 7, 2026, 5:09 p.m.
PD Predicate disambiguation batch_69fcc58566a0819082d5ea36e03bf0c6 completed May 7, 2026, 5:01 p.m.
Created at: May 3, 2026, 4:09 p.m.