Triple

T19880498
Position Surface form Disambiguated ID Type / Status
Subject Manishtushu E477755 entity
Predicate alternativeName P39 FINISHED
Object Maništuša NE NERFINISHED

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: Maništuša | Statement: [Manishtushu, alternativeName, Maništuša]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maništuša
Context triple: [Manishtushu, alternativeName, Maništuša]
  • A. Maništušu chosen
    Maništušu was an Akkadian king of the 23rd century BCE, traditionally regarded as a son and successor of Sargon of Akkad and known for expanding and consolidating the Akkadian Empire.
  • B. Pašman
    Pašman is a Croatian island and municipality in the Adriatic Sea, known for its picturesque coastline, traditional villages, and proximity to the city of Zadar.
  • C. Mentscha
    Mentscha is a small river or stream that serves as one of the tributaries feeding into Lake Murten in Switzerland.
  • D. Manić
    Manić is a small village located within the municipality of Barajevo in the Belgrade District of Serbia.
  • E. Vasishka
    Vasishka was a Kushan emperor who ruled parts of northern India and Central Asia in the early 3rd century CE, known primarily from his inscriptions and coinage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e658de4b288190a41bee67f570be1e completed April 20, 2026, 4:48 p.m.
Created at: April 10, 2026, 1:52 p.m.