Triple

T3390984
Position Surface form Disambiguated ID Type / Status
Subject Gajah Mada E71416 entity
Predicate sworeOath P9420 FINISHED
Object to unify the Nusantara under Majapahit rule 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: to unify the Nusantara under Majapahit rule | Statement: [Gajah Mada, sworeOath, to unify the Nusantara under Majapahit rule]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: sworeOath
Context triple: [Gajah Mada, sworeOath, to unify the Nusantara under Majapahit rule]
  • A. oath
    Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
  • B. swornInOn
    Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
  • C. oathSwornBefore
    Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
  • D. oathTakenBy chosen
    Indicates that an oath or formal promise has been made by a specific entity.
  • E. hasOathTo
    Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
  • 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_69ad85a9c4a88190a854019341cb3b60 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb6682c708190b76a7a16cee7c5aa completed March 8, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69adadf705608190975423779430cc58 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:14 p.m.