Triple
T27169525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Tongeren |
E682866
|
entity |
| Predicate | historicalSuccessorSee |
P58965
|
FINISHED |
| Object | Bishopric of Liège |
—
|
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: Bishopric of Liège | Statement: [Diocese of Tongeren, historicalSuccessorSee, Bishopric of Liège]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSuccessorSee Context triple: [Diocese of Tongeren, historicalSuccessorSee, Bishopric of Liège]
-
A.
historicalSuccessorState
Indicates that one state historically followed and replaced another state in time as its successor.
-
B.
successorSee
chosen
Indicates that one entity assumes or continues the role, position, or function previously held by another.
-
C.
historicalSuccessorInNationStateContext
Indicates that one political entity directly follows another as its successor within the historical continuity of a nation-state.
-
D.
chronologicallySucceededBy
Indicates that one event or state occurs later in time than, and thus follows, another.
-
E.
present-daySuccessor
Indicates that one entity is the current-day successor or continuation of another entity (e.g., an institution, organization, or administrative unit).
- F. None of above.
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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 9:22 a.m.