Triple
T6100126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roc |
E135971
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Rukhkh |
E515471
|
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: Rukhkh | Statement: [Roc, alternativeName, Rukhkh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rukhkh Context triple: [Roc, alternativeName, Rukhkh]
-
A.
Rakhsh
chosen
Rakhsh is the legendary, powerful warhorse of the Persian hero Rostam in the epic Shahnameh.
-
B.
Rohilla
The Rohilla are a Pashtun-origin community historically known for establishing the Rohilkhand region in northern India and playing a significant role in 18th-century North Indian politics.
-
C.
Rukmi
Rukmi is a character in Hindu mythology known as the proud and antagonistic brother of Rukmini, who opposed her marriage to Krishna.
-
D.
Rushani
Rushani is an Eastern Iranian language spoken primarily in the Rushan region of Tajikistan and neighboring areas.
-
E.
Harlakhi
Harlakhi is a town in the Madhubani district of Bihar, India, known for its proximity to the India–Nepal border and its association with the Mithila region.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3970808190ba90f5e4235db9f2 |
completed | March 22, 2026, 9:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1358d0e18819084e2acb9e75271b4 |
completed | March 23, 2026, 12:43 p.m. |
Created at: March 22, 2026, 4:13 p.m.