Triple
T12618370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakhisarai |
E301313
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Anga |
E473037
|
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: Anga | Statement: [Lakhisarai, historicalRegion, Anga]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anga Context triple: [Lakhisarai, historicalRegion, Anga]
-
A.
Anga
chosen
Anga was an ancient kingdom in the eastern Indian subcontinent, often noted in epic literature as the realm ruled by the warrior Karna.
-
B.
Angy
Angy is a diminutive or affectionate nickname commonly used for the given name Angela.
-
C.
Anjra
Anjra is a town in northern Morocco, historically notable as the birthplace of the Sufi scholar and Quran commentator Ibn ‘Ajiba.
-
D.
Esla
The Esla is a major river in northwestern Spain that flows through the provinces of León and Zamora before joining the Duero.
-
E.
Angi
Angi is a digital marketplace that connects homeowners with local contractors and service professionals for home improvement and repair projects.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d960c63ea48190ae1aae9280a023a6 |
completed | April 10, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65ed507988190b9d46586f3c3584c |
completed | May 2, 2026, 8:30 p.m. |
Created at: April 9, 2026, 5:13 p.m.