Triple
T14652257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulaghchi |
E344017
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | Jochid ulus |
E1078002
|
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: Jochid ulus | Statement: [Ulaghchi, memberOf, Jochid ulus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jochid ulus Context triple: [Ulaghchi, memberOf, Jochid ulus]
-
A.
Jochid ulus
chosen
Jochid ulus was the Mongol state in the western part of the empire that evolved into the Golden Horde under the descendants of Jochi.
-
B.
Koreets
Koreets was a Russian Imperial Navy gunboat that gained historical note for its role in the Russo-Japanese War, particularly during the opening naval actions near Chemulpo.
-
C.
Japo
Japo is a small settlement located on Arno Atoll in the Marshall Islands.
-
D.
両国
両国 is a district in Tokyo, Japan, best known for its sumo culture and the Ryōgoku Kokugikan sumo stadium.
-
E.
Jochid
The Jochid were the lineage and followers of Jochi, eldest son of Genghis Khan, forming the ruling house of the Golden Horde and other western Mongol domains.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb517e7648190b9fc73d6cdbb68de |
completed | April 14, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5d9ab188190934deb57fd6d9a56 |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:27 a.m.