Triple
T34442079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Spottiswood |
E884123
|
entity |
| Predicate | servedAsArchbishopOfStAndrewsFrom |
P200775
|
FINISHED |
| Object | 1615 |
—
|
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: 1615 | Statement: [John Spottiswood, servedAsArchbishopOfStAndrewsFrom, 1615]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsArchbishopOfStAndrewsFrom Context triple: [John Spottiswood, servedAsArchbishopOfStAndrewsFrom, 1615]
-
A.
servedAsArchbishopOfGlasgowFrom
Indicates that a person held and performed the role and duties of Archbishop of Glasgow starting from a specified date or time period.
-
B.
servedAsArchbishopOfGlasgowUntil
Indicates that a person held the position of Archbishop of Glasgow up to a specified end date or year.
-
C.
appointedAsArchbishopOfGlasgow
Indicates that a person has been formally appointed to the position of Archbishop of Glasgow.
-
D.
servedAsArchbishopOfYorkUntil
Indicates having held the position of Archbishop of York up to a specified end date or point in time.
-
E.
appointedAsArchbishopOfGlasgowBy
Indicates that one entity formally assigned another entity to the position of Archbishop of Glasgow.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
| PDg | Predicate description generation | batch_69ffac34c5948190be36de5781d91da3 |
completed | May 9, 2026, 9:50 p.m. |
Created at: May 1, 2026, 2 a.m.