Triple
T8340881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maung Maung Theik |
E195908
|
entity |
| Predicate | hasNamePart |
P5298
|
FINISHED |
| Object | Theik |
E728377
|
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: Theik | Statement: [Maung Maung Theik, hasNamePart, Theik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Theik Context triple: [Maung Maung Theik, hasNamePart, Theik]
-
A.
Theik
chosen
Theik is a Burmese surname associated with individuals such as Maung Maung Theik.
-
B.
Theur
Theur is a village near Pune in Maharashtra, India, known for its historic temples and association with the Peshwa-era Maratha nobility.
-
C.
Teok
Teok is a town in the Jorhat district of Assam, India, known as a local commercial and transportation hub in the region.
-
D.
Teke
Teke are a prominent Turkmen tribal group historically known for their influence in Central Asia and their famed Akhal-Teke horses.
-
E.
Teke
Teke is a Bantu language spoken primarily in the Republic of the Congo and neighboring Central African regions by the Teke people.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fe8989481909b32d4bfd586372d |
completed | March 31, 2026, 8:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde79e916c8190afc90c3b12c68caf |
completed | April 2, 2026, 3:50 a.m. |
Created at: March 30, 2026, 5:57 p.m.