Triple
T18457570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadeja |
E450942
|
entity |
| Predicate | titleUsed |
P29608
|
FINISHED |
| Object | Rao |
—
|
NE NERFINISHED |
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: Rao | Statement: [Jadeja, titleUsed, Rao]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rao Context triple: [Jadeja, titleUsed, Rao]
-
A.
Rao
chosen
Rao is a traditional honorific title used by certain Rajput clans in India, historically associated with nobility and local rulership.
-
B.
Rao Siha
Rao Siha was an early Rathore chieftain credited with establishing the Rathore presence in the Marwar region of present-day Rajasthan, India.
-
C.
Rajagopala
Rajagopala is a Hindu deity regarded as a form of Lord Krishna, particularly venerated as the divine cowherd and king of Gokul.
-
D.
Sikandra Rao
Sikandra Rao is a town in the Braj cultural region of Uttar Pradesh, India, known for its agrarian economy and regional trade.
-
E.
Sarvepalli
Sarvepalli is an Indian surname most prominently associated with Sarvepalli Radhakrishnan, the philosopher and statesman who served as the second President of India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7c18d88190ac17f58111722223 |
completed | April 19, 2026, 7:18 p.m. |
Created at: April 10, 2026, 11:31 a.m.