Triple
T16856790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1568 Edict of Torda |
E409803
|
entity |
| Predicate | place |
P373
|
FINISHED |
| Object | Torda |
E1099333
|
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: Torda | Statement: [1568 Edict of Torda, place, Torda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Torda Context triple: [1568 Edict of Torda, place, Torda]
-
A.
Torda
chosen
Torda is an alternative historical name for the Romanian city of Turda, known for its rich history and notable salt mine in Transylvania.
-
B.
Pallatanga
Pallatanga is a rural town and canton in central Ecuador known for its agricultural activities and scenic Andean surroundings.
-
C.
Tapolca
Tapolca is a small Hungarian town in the Transdanubian region, known for its scenic karst landscape and the famous Tapolca Lake Cave.
-
D.
Huși
Huși is a small city in eastern Romania known for its vineyards and wine production, located in the historical region of Western Moldavia.
-
E.
Trencsén
Trencsén is a historic town in present-day Slovakia, known for its medieval castle and its role as an important regional center in the former Upper Hungary.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37e34b88190bb4468424e2edf2d |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dbfb781881908f4d56f523e78f7a |
completed | May 10, 2026, 7:26 p.m. |
Created at: April 10, 2026, 5:24 a.m.