Triple
T19184127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Liège |
E469653
|
entity |
| Predicate | hasTerritory |
P285
|
FINISHED |
| Object | Hesbaye |
—
|
NE NERFINISHED |
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: Hesbaye | Statement: [Bishopric of Liège, hasTerritory, Hesbaye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hesbaye Context triple: [Bishopric of Liège, hasTerritory, Hesbaye]
-
A.
Hesbaye
chosen
Hesbaye is a historical region in present-day Belgium, known for its fertile agricultural land and early medieval significance within the Frankish realms.
-
B.
Blegny
Blegny is a municipality in eastern Belgium known for its historic coal mining heritage and rural character.
-
C.
Rocourt
Rocourt is a district of Liège in present-day Belgium, historically notable as the site of the 1746 Battle of Rocoux during the War of the Austrian Succession.
-
D.
Oesling
Oesling is the sparsely populated, hilly and forested northern region of Luxembourg, forming part of the Ardennes.
-
E.
Yvoir
Yvoir is a small municipality and village in the Walloon region of Belgium, known for its scenic location along the Meuse River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61f1d9c8190b67555383d821958 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 10, 2026, 12:07 p.m.