Triple
T12877907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig metropolitan region |
E308012
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Hartha |
E709504
|
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: Hartha | Statement: [Leipzig metropolitan region, containsCity, Hartha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hartha Context triple: [Leipzig metropolitan region, containsCity, Hartha]
-
A.
Hartha
chosen
Hartha is a small town in the German state of Saxony, known for its location within the rural region of Mittelsachsen.
-
B.
Harhaliana
Harhaliana is a small settlement associated with the Antikythera region in Greece.
-
C.
Haradh
Haradh is a major oil-producing area in eastern Saudi Arabia, known for hosting part of the vast Ghawar oil field and associated petroleum infrastructure.
-
D.
Harauti
Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
-
E.
Ypati
Ypati is a historic town in central Greece, known for its mountainous setting near Mount Oeta and its role in various periods of Greek history.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d970fa8474819086a8af3c90f3ca84 |
completed | April 10, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69bb83bac8190838f7537b806317c |
completed | May 3, 2026, 12:50 a.m. |
Created at: April 9, 2026, 5:38 p.m.