Triple
T26919140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of York (1237) |
E677596
|
entity |
| Predicate | confirmedScottishControlOf |
P165869
|
FINISHED |
| Object | Lothian |
—
|
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: Lothian | Statement: [Treaty of York (1237), confirmedScottishControlOf, Lothian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedScottishControlOf Context triple: [Treaty of York (1237), confirmedScottishControlOf, Lothian]
-
A.
ruledScotlandUntil
Indicates that a person or governing entity exercised ruling authority over Scotland up to a specified end time.
-
B.
confirmedEnglishControlOf
Indicates that one entity has verified or established that another entity holds authoritative control under English governance or influence.
-
C.
ScottishStrategy
Indicates a strategic plan, policy, or approach that is specifically associated with or implemented in the context of Scotland.
-
D.
impactOnScotland
Indicates the effect or consequences that something has specifically on Scotland.
-
E.
hasCapitalCityOfScotland
Indicates the relationship in which an entity has, as its capital city, the city that serves as the capital of Scotland.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 27, 2026, 6:06 a.m.