Triple
T13562124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E81 |
E323933
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Turda |
E358030
|
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: Turda | Statement: [European route E81, connects, Turda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Turda Context triple: [European route E81, connects, Turda]
-
A.
Turda
chosen
Turda is a historic town in central Romania’s Transylvania region, known for its ancient salt mine and significant Roman and medieval heritage.
-
B.
Turóc
Turóc is a historical region in present-day northern Slovakia, centered around the Turiec River valley and the town of Martin, known for its cultural and national significance to Slovaks.
-
C.
Tivissa
Tivissa is a historic village in Catalonia, Spain, known for its scenic setting among the mountains of the Ribera d’Ebre region and its well-preserved medieval core.
-
D.
Tura
Tura is a prominent town in the Indian state of Meghalaya, serving as a major administrative, cultural, and economic center in the Garo Hills region.
-
E.
Tura
Tura is a district in southern Cairo, Egypt, historically known for its limestone quarries used in ancient Egyptian monuments.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff5219081909cf60423e79d278f |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75dad601481908de5f266f01f3f49 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.