Triple
T5606667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone of Destiny |
E147249
|
entity |
| Predicate | dateMovedTo |
P4158
|
FINISHED |
| Object | 1296 (to Westminster Abbey) |
—
|
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: 1296 (to Westminster Abbey) | Statement: [Stone of Destiny, dateMovedTo, 1296 (to Westminster Abbey)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateMovedTo Context triple: [Stone of Destiny, dateMovedTo, 1296 (to Westminster Abbey)]
-
A.
dateMovedToParentAgency
Indicates the date on which an entity was transferred to, or came under the authority of, its parent agency.
-
B.
movementDate
chosen
Indicates the date on which a movement, transfer, or relocation event occurs.
-
C.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
D.
deFactoTransferDate
Indicates the date on which control or ownership is effectively transferred in practice, regardless of the formal or legal transfer date.
-
E.
treasuryMovedOn
Indicates that a treasury or central financial fund has been transferred or relocated from one place, account, or controlling entity to another at a specific point in time.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fbb8748190841e5e09db3feef1 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.