Triple
T4958839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Fulham |
E111352
|
entity |
| Predicate | currentIncumbentStartYear |
P61436
|
FINISHED |
| Object | 2013 |
—
|
LITERAL FINISHED |
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: 2013 | Statement: [Bishop of Fulham, currentIncumbentStartYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentIncumbentStartYear Context triple: [Bishop of Fulham, currentIncumbentStartYear, 2013]
-
A.
currentLegislatureStartYear
Indicates the calendar year in which the currently serving legislature (or legislative term) officially began.
-
B.
currentSpeakerAssumedOffice
Indicates that the person who is currently serving as speaker has taken up or begun holding a particular office or position.
-
C.
inaugurationYear
Indicates the calendar year in which an entity was formally inaugurated or officially brought into operation.
-
D.
representedInCongressSince
Indicates that an entity has served as a representative in a legislative congress continuously since a specified date or time.
-
E.
inauguralClassYear
Indicates the year in which the first (inaugural) class or cohort associated with an entity began or was established.
- F. None of above. chosen
Provenance (4 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:32 p.m.