Triple
T13846635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piasts of Bytom |
E332823
|
entity |
| Predicate | hasTerritory |
P285
|
FINISHED |
| Object | Bytom |
E104306
|
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: Bytom | Statement: [Piasts of Bytom, hasTerritory, Bytom]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bytom Context triple: [Piasts of Bytom, hasTerritory, Bytom]
-
A.
Bytom
chosen
Bytom is an industrial city in southern Poland’s Silesian region, known for its mining heritage and historical urban architecture.
-
B.
Bantumi
Bantumi is a digital version of the traditional Mancala-style board game that was popularized on early Nokia mobile phones.
-
C.
Borotiam
Borotiam is a village located on the atoll of Abaiang in the island nation of Kiribati in the central Pacific Ocean.
-
D.
Barabai
Barabai is a town and administrative center in Hulu Sungai Tengah Regency on the island of Borneo in Indonesia’s South Kalimantan province.
-
E.
Bori
Bori is a prominent urban center in Nigeria’s Rivers State, serving as an important commercial and administrative hub for the surrounding region.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b1a25c8190a9f85ba43c421188 |
completed | April 14, 2026, 9:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0f189008190bb9afeef42564a33 |
completed | May 3, 2026, 9:41 p.m. |
Created at: April 9, 2026, 10:13 p.m.