Triple
T17368687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruzyně |
E422250
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Střešovice |
—
|
NE NERFINISHED |
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: Střešovice | Statement: [Ruzyně, locatedNear, Střešovice]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Střešovice Context triple: [Ruzyně, locatedNear, Střešovice]
-
A.
Střešovice
chosen
Střešovice is a residential district in Prague known for its historic villas, quiet streets, and proximity to Prague Castle.
-
B.
Hlušovice
Hlušovice is a small municipality and village in the Olomouc Region of the Czech Republic.
-
C.
Vršovice
Vršovice is a district in Prague, Czech Republic, known for its residential neighborhoods, sports facilities, and historic architecture.
-
D.
Bubeneč
Bubeneč is a residential and diplomatic district in Prague known for its embassies, green spaces, and proximity to Stromovka park.
-
E.
Milovice
Milovice is a town in the Czech Republic known for its rapid post-military redevelopment and location northeast of Prague in the Central Bohemian Region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6790448190a24047523a019f81 |
completed | April 19, 2026, 2:13 a.m. |
Created at: April 10, 2026, 5:44 a.m.