Triple
T1379122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linlithgow Palace |
E29295
|
entity |
| Predicate | majorFireDate |
P27137
|
FINISHED |
| Object | 1746 |
—
|
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: 1746 | Statement: [Linlithgow Palace, majorFireDate, 1746]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorFireDate Context triple: [Linlithgow Palace, majorFireDate, 1746]
-
A.
majorRevisionDate
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
B.
majorRevisionYear
Indicates the year in which a significant or primary revision of something (such as a work, document, or standard) was made.
-
C.
majorMine
Indicates that a mine is classified as a major or primary mining site, typically based on its scale, output, or importance.
-
D.
majorStatus
Indicates that an entity holds primary or most significant status relative to others in a given context.
-
E.
escalationDate
Indicates the date on which an issue, case, or situation was formally escalated to a higher level of attention or authority.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3187f248190a5813274b0ef944d |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.