Triple
T10786410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirhuta |
E254461
|
entity |
| Predicate | scriptCodeISO15924 |
P11937
|
FINISHED |
| Object | Tirh |
E254461
|
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: Tirh | Statement: [Tirhuta, scriptCodeISO15924, Tirh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tirh Context triple: [Tirhuta, scriptCodeISO15924, Tirh]
-
A.
Tirico
Tirico is the surname of American sportscaster Mike Tirico, known for his play-by-play work on major sports broadcasts.
-
B.
Tirhuta
chosen
Tirhuta is a historical Brahmic script traditionally used for writing the Maithili language in the Mithila region of India and Nepal.
-
C.
Tiriyó-Tarëno
Tiriyó-Tarëno is an indigenous Cariban language spoken by the Tiriyó people in parts of Brazil and Suriname.
-
D.
Tirora
Tirora is a town in the Gondia district of Maharashtra, India, known for its agricultural surroundings and regional commercial activity.
-
E.
Tialo
Tialo is an Austronesian language of the Tomini–Tolitoli subgroup spoken in Central Sulawesi, Indonesia.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d5422481908d7ab833c6cbc879 |
completed | April 9, 2026, 5:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de56199d088190938a72105540cf66 |
completed | April 14, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:17 p.m.