Triple
T26095641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Haddington |
E658256
|
entity |
| Predicate | signedDuringRegencyOf |
P109327
|
FINISHED |
| Object | Mary of Guise |
—
|
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: Mary of Guise | Statement: [Treaty of Haddington, signedDuringRegencyOf, Mary of Guise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedDuringRegencyOf Context triple: [Treaty of Haddington, signedDuringRegencyOf, Mary of Guise]
-
A.
signedUnderRegencyOf
chosen
Indicates that a document or agreement was formally signed by one party while another individual or authority exercised regency, acting as the legal representative or guardian of the signer.
-
B.
recognizedAsRegent
Indicates that an entity is formally acknowledged or designated as serving in the role of regent for another.
-
C.
periodOfRegency
Indicates the time span during which a regent exercised authority on behalf of the rightful ruler.
-
D.
signedDuringGovernmentOf
Indicates that a signing event occurred while a specified government or administration was in power.
-
E.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 7:50 p.m.