Triple
T2242503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claim of Right Act 1689 (Scotland) |
E49427
|
entity |
| Predicate | preUnion |
P28036
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Claim of Right Act 1689 (Scotland), preUnion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preUnion Context triple: [Claim of Right Act 1689 (Scotland), preUnion, yes]
-
A.
preUnionRight
chosen
Indicates that the subject entity existed or held a status immediately before a union or merging event involving the object entity.
-
B.
preUnionLegislativeChamber
Indicates that a legislative chamber existed and functioned before a political union or unification of states or territories took place.
-
C.
postUnionRepresentation
Indicates that an entity serves as a representative or representation of another entity after a union or merger has taken place.
-
D.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
-
E.
unites
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
- 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0c017548190a71fb4a0e2a8189f |
completed | March 7, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.