Triple
T5949284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jilava Prison |
E132356
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Jilava |
E132356
|
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: Jilava | Statement: [Jilava Prison, locatedIn, Jilava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jilava Context triple: [Jilava Prison, locatedIn, Jilava]
-
A.
Jilava
chosen
Jilava is a locality in Romania best known for its historic prison and fortress, which were used for political detentions and executions, especially during the 20th century.
-
B.
Lučina
Lučina is a river in the Moravian-Silesian Region of the Czech Republic that flows through the city of Ostrava.
-
C.
Bílina
Bílina is a river in the Czech Republic that flows through the Ústí nad Labem Region and is known for passing through several industrial and mining areas.
-
D.
Jalesar
Jalesar is a town in the Braj cultural region of northern India, known for its traditional brassware and temple heritage.
-
E.
Javorná
Javorná is a small river in the Czech Republic that serves as a tributary of the Úhlava River.
- 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_69c00869d3308190af89b2453e0f7546 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0397deea08190b9397d0413740300 |
completed | March 22, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0e3c4120c8190bab97f91a7bc7030 |
completed | March 23, 2026, 6:55 a.m. |
Created at: March 22, 2026, 4:02 p.m.