Triple
T8564568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cilappatikāram |
E202771
|
entity |
| Predicate | setInCity |
P7747
|
FINISHED |
| Object | Puhar |
E740543
|
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: Puhar | Statement: [Cilappatikāram, setInCity, Puhar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Puhar Context triple: [Cilappatikāram, setInCity, Puhar]
-
A.
Puhar
chosen
Puhar is an ancient port city of the Chola kingdom in Tamil Nadu, India, renowned in Tamil literature and history as a major center of trade and culture.
-
B.
Vashpa
Vashpa is a figure in early Buddhist tradition known as one of the disciples present at the Buddha’s first sermon, the Turning of the Wheel of Dharma.
-
C.
Puah
Puah is a minor biblical figure mentioned in the Old Testament as part of the genealogy of the tribe of Issachar.
-
D.
Pákozd
Pákozd is a Hungarian village in Fejér County known for its proximity to Lake Velence and its historical significance, including an important 1848 revolutionary battle.
-
E.
Piro
Piro is a town in the Bhojpur district of Bihar, India, known as one of the district’s principal urban and commercial centers.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9d11274819099cc33a21a993a1f |
completed | March 31, 2026, 3:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce89677888819091dfda14ce6baef3 |
completed | April 2, 2026, 3:21 p.m. |
Created at: March 30, 2026, 6:20 p.m.