Triple
T38304292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Fotheringhay (1586) |
E1032304
|
entity |
| Predicate | dateBefore |
P81955
|
FINISHED |
| Object | execution of Mary, Queen of Scots |
—
|
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: execution of Mary, Queen of Scots | Statement: [Treaty of Fotheringhay (1586), dateBefore, execution of Mary, Queen of Scots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateBefore Context triple: [Treaty of Fotheringhay (1586), dateBefore, execution of Mary, Queen of Scots]
-
A.
createdBefore
Indicates that one entity was created at an earlier time than another entity.
-
B.
locatedInTimeBefore
chosen
Indicates that one temporal event or interval occurs entirely before another in time.
-
C.
notEarlierThan
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
-
D.
timeSpanEndsBefore
Indicates that one time span concludes entirely before the starting point of another time span, with no overlap between them.
-
E.
meetsInPast
Indicates that two entities encountered or came together at some point in the past.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.