Triple
T2623677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directory for Public Worship |
E59066
|
entity |
| Predicate | yearAdoptedInScotland |
P1362
|
FINISHED |
| Object | 1645 |
—
|
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: 1645 | Statement: [Directory for Public Worship, yearAdoptedInScotland, 1645]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearAdoptedInScotland Context triple: [Directory for Public Worship, yearAdoptedInScotland, 1645]
-
A.
ruledScotlandUntil
Indicates that a person or governing entity exercised ruling authority over Scotland up to a specified end time.
-
B.
dateAdopted
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
C.
hasCapitalCityOfScotland
Indicates the relationship in which an entity has, as its capital city, the city that serves as the capital of Scotland.
-
D.
officialAdoptionYear
chosen
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
-
E.
yearEnteredIntoForce
Indicates the year in which an agreement, law, treaty, or similar instrument officially became legally effective or operational.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.