Triple
T13452914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samastipur |
E311154
|
entity |
| Predicate | hasRailConnectivityTo |
P58937
|
FINISHED |
| Object | Siwan |
E295115
|
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: Siwan | Statement: [Samastipur, hasRailConnectivityTo, Siwan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Siwan Context triple: [Samastipur, hasRailConnectivityTo, Siwan]
-
A.
Siwan
chosen
Siwan is a town and district headquarters in the Indian state of Bihar, known for its historical significance and political prominence.
-
B.
Siwan
Siwan is the Welsh name for Joan, Lady of Wales, the illegitimate daughter of King John of England and wife of Llywelyn the Great.
-
C.
Samanta
Samanta was a feudal title in early medieval India, often denoting subordinate rulers or vassal chiefs under larger regional dynasties.
-
D.
Suri
Suri is a town in the Indian state of West Bengal known as an administrative and commercial center of the Birbhum region.
-
E.
Suri
Suri is an Etruscan deity often associated with the underworld, darkness, and chthonic powers.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaefae85481909e6a59797cbb25e7 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7399c539c819080802b620da6fcfc |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:41 p.m.