Triple

T28219169
Position Surface form Disambiguated ID Type / Status
Subject Tatenokai E711401 entity
Predicate actionDuringIncident P51060 FINISHED
Object attempted coup d’état appeal to Self-Defense Forces 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: attempted coup d’état appeal to Self-Defense Forces | Statement: [Tatenokai, actionDuringIncident, attempted coup d’état appeal to Self-Defense Forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: actionDuringIncident
Context triple: [Tatenokai, actionDuringIncident, attempted coup d’état appeal to Self-Defense Forces]
  • A. missionDuringIncident
    Indicates that a mission or operation took place concurrently with, or in the context of, a specific incident.
  • B. incidentWith
    Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with another entity.
  • C. attackOccurred chosen
    Indicates that an act of aggression or violence was carried out by one party against another.
  • D. sawActionDuring
    Indicates that one entity observed an action or event occurring within a specific time period or during another event.
  • E. incidentName
    Indicates the specific name or label assigned to an incident within a system or context.
  • 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_69efb51cb5288190818c1f63a266af11 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f6434f9f888190bd43fde92cd729fe completed May 2, 2026, 6:32 p.m.
PD Predicate disambiguation batch_69f641e0fde08190bf06a1c5b388aa84 completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 10:45 p.m.