Triple
T15954800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ermengarde of Hesbaye |
E386906
|
entity |
| Predicate | historicalRegionOfOrigin |
P3743
|
FINISHED |
| Object |
Hesbaye
Hesbaye is a historical region in present-day Belgium, known for its fertile agricultural land and early medieval significance within the Frankish realms.
|
E1196217
|
NE FINISHED |
How this triple was built (4 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: [Ermengarde of Hesbaye, historicalRegionOfOrigin, Hesbaye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hesbaye Context triple: [Ermengarde of Hesbaye, historicalRegionOfOrigin, Hesbaye]
-
A.
Blegny
Blegny is a municipality in eastern Belgium known for its historic coal mining heritage and rural character.
-
B.
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.
-
C.
Oesling
Oesling is the sparsely populated, hilly and forested northern region of Luxembourg, forming part of the Ardennes.
-
D.
Yvoir
Yvoir is a small municipality and village in the Walloon region of Belgium, known for its scenic location along the Meuse River.
-
E.
Comines
Comines is a town situated along the Lys River in the historic Flanders region on the border between France and Belgium.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hesbaye Triple: [Ermengarde of Hesbaye, historicalRegionOfOrigin, Hesbaye]
Generated description
Hesbaye is a historical region in present-day Belgium, known for its fertile agricultural land and early medieval significance within the Frankish realms.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Hesbaye Target entity description: Hesbaye is a historical region in present-day Belgium, known for its fertile agricultural land and early medieval significance within the Frankish realms.
-
A.
Blegny
Blegny is a municipality in eastern Belgium known for its historic coal mining heritage and rural character.
-
B.
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.
-
C.
Oesling
Oesling is the sparsely populated, hilly and forested northern region of Luxembourg, forming part of the Ardennes.
-
D.
Yvoir
Yvoir is a small municipality and village in the Walloon region of Belgium, known for its scenic location along the Meuse River.
-
E.
Comines
Comines is a town situated along the Lys River in the historic Flanders region on the border between France and Belgium.
- F. None of above. chosen
Provenance (5 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156f94b108190905d295c3405860e |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff291a4308190bd5b45dfdb3a6b98 |
completed | May 10, 2026, 2:50 a.m. |
| NEDg | Description generation | batch_69fff35ded288190b4d261358f1661cb |
completed | May 10, 2026, 2:54 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fff3f2760c8190a58fedc2798614ae |
completed | May 10, 2026, 2:56 a.m. |
Created at: April 10, 2026, 4:53 a.m.