Triple
T22208483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godfrey I, Count of Louvain |
E548877
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Count of Brussels |
C45956
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Count of Brussels Context triple: [Godfrey I, Count of Louvain, instanceOf, Count of Brussels]
-
A.
borough of Antwerp
The borough of Antwerp is an administrative subdivision of the city of Antwerp, encompassing specific neighborhoods and local governance structures within the wider municipality.
-
B.
Count of Flanders
The Count of Flanders was a medieval noble title denoting the ruler of the County of Flanders, a powerful feudal principality in northwestern Europe that played a key role in regional politics, trade, and warfare.
-
C.
Count of Luxembourg
A Count of Luxembourg is a noble title historically held by the feudal rulers of the County of Luxembourg, signifying territorial lordship, aristocratic status, and dynastic authority within the medieval and early modern European nobility.
-
D.
public body of Belgium
A public body of Belgium is an organization established by law at the federal, regional, community, provincial, or municipal level to perform public tasks, manage public services, or exercise administrative authority on behalf of the Belgian state.
-
E.
Count of Holland
The Count of Holland was the medieval and early modern noble title held by the ruler of the County of Holland, a significant feudal territory in what is now the western Netherlands.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:36 p.m.