Triple
T12181990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebeș |
E290242
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Sebeșul Săsesc |
E290242
|
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: Sebeșul Săsesc | Statement: [Sebeș, historicalName, Sebeșul Săsesc]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sebeșul Săsesc Context triple: [Sebeș, historicalName, Sebeșul Săsesc]
-
A.
Sebeș
chosen
Sebeș is a historic town in central Romania’s Transylvania region, notable as an important medieval center of the Transylvanian Saxon community.
-
B.
Săcele
Săcele is a town in central Romania known for its proximity to the city of Brașov and its location in the Carpathian Mountains region.
-
C.
Sebeș River
The Sebeș River is a tributary watercourse that flows through central Romania, contributing to the larger Mureș (Maros) River system.
-
D.
Reșița
Reșița is an industrial city in western Romania, historically known as a major center of steel production and engineering in the Banat region.
-
E.
Crișul Repede
Crișul Repede is a fast-flowing river in western Romania that runs through the Crișana region and is an important tributary of the Körös (Criș) river system.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fd8dac8190928059ad2b6bbbf3 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6acee6481908ee4129956c98c52 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:50 p.m.