Triple
T8352195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liluah Railway Workshop |
E196587
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Liluah |
E196587
|
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: Liluah | Statement: [Liluah Railway Workshop, locatedIn, Liluah]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Liluah Context triple: [Liluah Railway Workshop, locatedIn, Liluah]
-
A.
Liluah
chosen
Liluah is a suburban locality in the Howrah district of West Bengal, India, known for its residential areas and railway facilities near Kolkata.
-
B.
Eliada
Eliada is a lesser-known biblical figure mentioned in the Old Testament as one of King David’s sons.
-
C.
Lakalai
Lakalai is an Oceanic language spoken by an indigenous community in Papua New Guinea.
-
D.
Tynaarlo
Tynaarlo is a municipality in the northeastern Netherlands known for its rural character and location between the cities of Groningen and Assen.
-
E.
Laiolo
Laiolo is an alternate name for the Laiyolo language, an Austronesian language spoken in parts of 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80460f048190aa298ddffde1047d |
completed | March 31, 2026, 8:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc75623488190be3303f5e75784e8 |
completed | April 2, 2026, 1:33 a.m. |
Created at: March 30, 2026, 5:59 p.m.