Triple
T8206498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plovdiv |
E191700
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Pulpudeva |
E491012
|
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: Pulpudeva | Statement: [Plovdiv, historicalName, Pulpudeva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pulpudeva Context triple: [Plovdiv, historicalName, Pulpudeva]
-
A.
Pulpudeva
chosen
Pulpudeva is the ancient Thracian name for the city later known as Philippopolis, a major historical center in what is now Plovdiv, Bulgaria.
-
B.
Mahadeva
Mahadeva is a principal form of the Hindu god Shiva, revered as the supreme deity and great lord in Shaivism.
-
C.
Pandurang
Pandurang is the father of Ramachandra Pandurang Tope, better known as the Indian independence fighter Tatya Tope.
-
D.
Nandideva
Nandideva is a revered form of Nandi, the sacred bull and devoted mount and gatekeeper of the Hindu god Shiva.
-
E.
Narayana
Narayana is a revered name of the Hindu god Vishnu, especially associated with his role as the supreme preserver and sustainer of the universe.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb726b520081908ce4a03bd14dfcdf |
completed | March 31, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccedd27bc08190a8109217069a8978 |
completed | April 1, 2026, 10:05 a.m. |
Created at: March 30, 2026, 5:43 p.m.