Triple
T28662088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tullum Leucorum |
E725493
|
entity |
| Predicate | laterEcclesiasticalSee |
P173670
|
FINISHED |
| Object | Bishopric of Toul |
—
|
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 Toul | Statement: [Tullum Leucorum, laterEcclesiasticalSee, Bishopric of Toul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEcclesiasticalSee Context triple: [Tullum Leucorum, laterEcclesiasticalSee, Bishopric of Toul]
-
A.
laterChristianBishopric
chosen
Indicates that a place or see later became the seat of a Christian bishopric, even if it was not one originally.
-
B.
dioceseLater
Indicates that one diocese exists or is established later in time than another diocese.
-
C.
modernSuccessorDiocese
Indicates that one diocese is the present-day or contemporary successor to an earlier, historically related diocese.
-
D.
otherHistoricArchiepiscopalSee
Indicates that an entity has or is associated with another historic archiepiscopal see distinct from its primary one.
-
E.
majorArchepiscopalSee
Indicates that one entity serves as the principal episcopal jurisdiction (major archiepiscopal see) governing or presiding over the other within a particular church or rite.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 28, 2026, 4:58 a.m.