Triple
T12649689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Taksin |
E302123
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Taksin |
E634312
|
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: Taksin | Statement: [King Taksin, name, Taksin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taksin Context triple: [King Taksin, name, Taksin]
-
A.
Taksin
chosen
Taksin was an 18th-century Siamese king who reunified the country after the fall of Ayutthaya and established Thonburi as the capital.
-
B.
Taksim
Taksim is a central district and major transportation and cultural hub on the European side of Istanbul, Turkey.
-
C.
Taksi
Taksi was a Jurchen chieftain of the late Ming period and the father of Nurhaci, whose lineage helped lay the foundations for the later Qing dynasty.
-
D.
Citura
Citura is the public transport operator responsible for managing Reims’ urban transit network, including its tramway system, in northeastern France.
-
E.
Pajak
Pajak is a surname of Polish origin, often rendered without diacritics from the original form "Pająk."
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9615cf6f48190bd0983cf7465ab15 |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6687dad6c8190bb72bfebf6636a37 |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:18 p.m.