Triple
T10832851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Longdon |
E255665
|
entity |
| Predicate | hasCommemorativeDate |
P865
|
FINISHED |
| Object | annual remembrance around 11–12 June |
—
|
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: annual remembrance around 11–12 June | Statement: [Mount Longdon, hasCommemorativeDate, annual remembrance around 11–12 June]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorativeDate Context triple: [Mount Longdon, hasCommemorativeDate, annual remembrance around 11–12 June]
-
A.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
B.
periodCommemorated
Indicates that something serves to honor, remember, or mark a specific historical or temporal period.
-
C.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
D.
commemoratedOn
chosen
Indicates that something is remembered, honored, or celebrated on a specific date or occasion.
-
E.
previouslyCommemoratedBy
Indicates that an entity was honored or remembered in the past through a specific commemorative act, object, or event.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7442439dc8190af59f9c8d0637c01 |
completed | April 9, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.