Triple

T22440192
Position Surface form Disambiguated ID Type / Status
Subject 上皇 E554732 entity
Predicate roleLimitation P99 FINISHED
Object 国政に関する権能を持たない点は天皇と同様 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: 国政に関する権能を持たない点は天皇と同様 | Statement: [上皇, roleLimitation, 国政に関する権能を持たない点は天皇と同様]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleLimitation
Context triple: [上皇, roleLimitation, 国政に関する権能を持たない点は天皇と同様]
  • A. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • B. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • C. securityLimitation
    Indicates a constraint, restriction, or boundary imposed for security purposes on what actions, access, or operations are allowed between entities.
  • D. accessRestrictedTo
    Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
  • E. accessRestriction
    Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
  • 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_69e11e5010e48190ae1e9c9db9697637 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15ae0edcc8190919b198035de0df2 completed April 29, 2026, 1:12 a.m.
PD Predicate disambiguation batch_69e898a327948190beee5e168006a0a7 completed April 22, 2026, 9:45 a.m.
Created at: April 16, 2026, 8:47 p.m.