Triple
T15890692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ieng Sary |
E385309
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Sary |
E813573
|
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: Sary | Statement: [Ieng Sary, givenName, Sary]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sary Context triple: [Ieng Sary, givenName, Sary]
-
A.
Sary
chosen
Sary is a surname that functions as a variant spelling of the family name Sari, found in various cultural and linguistic contexts.
-
B.
Sarayan
Sarayan is a small city in eastern Iran known as an administrative and agricultural center within South Khorasan Province.
-
C.
Saryk
The Saryk are a historically significant Turkmen tribe known for their distinct cultural traditions and contributions to the ethnogenesis of the Turkmen people in Central Asia.
-
D.
Sayran
Sayran is a metro station on the Almaty Metro system in Almaty, Kazakhstan.
-
E.
Saryati
Saryati is a figure in Hindu mythology known as one of the sons of the progenitor Shraddhadeva Manu and a king mentioned in ancient texts.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561e5ac481908ead7de3140c769d |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb047b6248190b6c11ef20636f50f |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:51 a.m.