Triple

T4958656
Position Surface form Disambiguated ID Type / Status
Subject Sulak E111348 entity
Predicate familyName P18 FINISHED
Object Sivaraksa E114005 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: Sivaraksa | Statement: [Sulak, familyName, Sivaraksa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sivaraksa
Context triple: [Sulak, familyName, Sivaraksa]
  • A. Sivaraksa chosen
    Sivaraksa is the surname of Sulak Sivaraksa, a prominent Thai social activist, intellectual, and proponent of engaged Buddhism.
  • B. Sakaar
    Sakaar is a chaotic, trash-covered planet ruled by the Grandmaster in the Marvel Cinematic Universe, known for its gladiatorial contests and bizarre cosmic detritus.
  • C. Sokar
    Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
  • D. Sirokakara
    Sirokakara is a small settlement located on Choiseul Island in the Solomon Islands.
  • E. Sikma
    Sikma is a surname most notably associated with Jack Sikma, a Hall of Fame American basketball player known for his successful NBA career with the Seattle SuperSonics.
  • 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_69bd4418390c8190b7e9766a2512ce55 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd71d957cc8190b82fdd1ca61924bf completed March 20, 2026, 4:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69be81e4ccc4819090223633fdb04eee completed March 21, 2026, 11:32 a.m.
Created at: March 20, 2026, 1:32 p.m.