Triple
T19603485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trnava |
E470542
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Slovak Rome |
—
|
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: Slovak Rome | Statement: [Trnava, nickname, Slovak Rome]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Slovak Rome Context triple: [Trnava, nickname, Slovak Rome]
-
A.
Slovak Rome
chosen
Slovak Rome is a nickname for the Slovak city of Trnava, known for its numerous historic churches and strong Catholic heritage.
-
B.
Malacky
Malacky is a small town in western Slovakia known for its historical center and location near the capital, Bratislava.
-
C.
Kolínska
Kolínska is a Slovak surname most notably borne by the actress and singer Zora Kolínska.
-
D.
Pápa
Pápa is a Hungarian town that hosts a key NATO Strategic Airlift Capability air base, making it an important military and logistics hub in Central Europe.
-
E.
Mladá
Mladá is a locality in the Czech Republic known primarily as a former military area that now forms an administrative part of the town of Milovice.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64081af6c8190868b73b07c874cd5 |
completed | April 20, 2026, 3:04 p.m. |
Created at: April 10, 2026, 1:43 p.m.