Triple
T10596577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scots Guards memorial on Mount Tumbledown |
E250129
|
entity |
| Predicate | hasYearOfEventCommemorated |
P13724
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Scots Guards memorial on Mount Tumbledown, hasYearOfEventCommemorated, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearOfEventCommemorated Context triple: [Scots Guards memorial on Mount Tumbledown, hasYearOfEventCommemorated, 1982]
-
A.
commemoratedYear
chosen
Indicates the specific year in which an event, person, or entity is formally remembered, honored, or celebrated.
-
B.
hasYearOfNamesakeEvent
Indicates the specific year in which the event that a namesake is based on or named after took place.
-
C.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
-
D.
commemoratesPersonBirthYear
Indicates that something is intended to honor or mark the year in which a specific person was born.
-
E.
commemoratesEventOn
Indicates that one entity marks, honors, or observes a specific event on a particular date or occasion.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278dacc4819089b759744f100e5f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.