Triple

T15728502
Position Surface form Disambiguated ID Type / Status
Subject Futuh-us-Salatin E381279 entity
Predicate author P4 FINISHED
Object Isami E381279 NE 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: Isami | Statement: [Futuh-us-Salatin, author, Isami]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Isami
Context triple: [Futuh-us-Salatin, author, Isami]
  • A. Isami chosen
    Isami was a 14th-century Indian historian and poet best known for his Persian chronicle "Futuh-us-Salatin," which records the political and military history of the Delhi Sultanate, including the Mongol invasions of India.
  • B. Atsuhito
    Atsuhito was the personal name of Emperor Daigo, a 10th-century Japanese emperor of the Heian period.
  • C. Takatoshi
    Takatoshi is a masculine Japanese given name that can be written with various kanji combinations and is borne by multiple notable individuals in Japan.
  • D. Asahiko
    Asahiko is the given name of Prince Kuni Asahiko, a member of the Japanese imperial family during the late Edo and early Meiji periods.
  • E. Takahito
    Takahito, better known by his title Prince Mikasa, was a member of the Japanese imperial family and the youngest son of Emperor Taishō.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d86d9cdb648190bf3171be0bd7d872 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04fb4cc0081909efe330339474017 completed April 16, 2026, 2:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0084a6d6308190ad57a51b380171a2 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 4:46 a.m.