Triple
T14299473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danapur subdivision |
E354523
|
entity |
| Predicate | administrativeCentre |
P1474
|
FINISHED |
| Object | Danapur |
E354522
|
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: Danapur | Statement: [Danapur subdivision, administrativeCentre, Danapur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Danapur Context triple: [Danapur subdivision, administrativeCentre, Danapur]
-
A.
Danapur
chosen
Danapur is a cantonment town near Patna in the Indian state of Bihar, known for its historical military significance and role as a major railway junction.
-
B.
Dinas
Dinas is a village in Gwynedd, Wales, known as a key station and junction on the heritage Welsh Highland Railway near Caernarfon.
-
C.
Damrak
Damrak is a central street and canal in Amsterdam that runs from Amsterdam Centraal Station toward Dam Square, forming one of the city’s main tourist and commercial arteries.
-
D.
Nawada
Nawada is a town and administrative center in eastern India known for being the headquarters of Nawada district in the state of Bihar.
-
E.
Duri
Duri is an Austronesian language spoken by the Duri people of South Sulawesi, Indonesia.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717e246c819083e67ac2b3b77881 |
completed | April 14, 2026, 4:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4682f86881908c9fb210bb9e486a |
completed | May 8, 2026, 2:12 a.m. |
Created at: April 10, 2026, 1:11 a.m.