Triple
T17045267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levoča |
E413550
|
entity |
| Predicate | wasFreeRoyalTown |
P82213
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Levoča, wasFreeRoyalTown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFreeRoyalTown Context triple: [Levoča, wasFreeRoyalTown, true]
-
A.
wasFreeImperialCityOf
Indicates that an entity formerly held the status of a Free Imperial City within the Holy Roman Empire in relation to another specified entity (typically the empire or its imperial structure).
-
B.
wasRoyalBurgh
chosen
Indicates that a town or settlement held the official legal status of a royal burgh, having been granted specific rights and privileges directly by the monarch.
-
C.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
D.
liberatedCity
Indicates that an agent has freed a city from control, occupation, or oppression.
-
E.
ruledCity
Indicates that a person or governing entity exercised political authority or control over a specific city.
- F. None of above.
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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9d7e988190a5e3991c7123f9b0 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.