Triple
T11999767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guru Amar Das |
E285626
|
entity |
| Predicate | placeOfDeath |
P21
|
FINISHED |
| Object | Goindwal |
E556459
|
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: Goindwal | Statement: [Guru Amar Das, placeOfDeath, Goindwal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goindwal Context triple: [Guru Amar Das, placeOfDeath, Goindwal]
-
A.
Goindwal
chosen
Goindwal is a historic Sikh town in Punjab, India, renowned as an early center of Sikhism and a significant pilgrimage site associated with several Sikh Gurus.
-
B.
Gwalchmei
Gwalchmei is the Welsh name for Sir Gawain, a prominent knight of the Round Table in Arthurian legend renowned for his bravery and chivalry.
-
C.
Burcwen
Burcwen is a character associated with Godric, likely appearing in narratives or stories centered around him.
-
D.
Esgalduin
Esgalduin is a river in J.R.R. Tolkien’s Middle-earth, most notably flowing through the forest realm of Doriath.
-
E.
Garwolin
Garwolin is a town in eastern Poland, located in the Masovian Voivodeship southeast of Warsaw.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c26d7881909b67a31d04882eb5 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f472917ed08190a872d9e5663d5ed5 |
completed | May 1, 2026, 9:29 a.m. |
Created at: April 8, 2026, 9:46 p.m.