Triple
T30620466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remembrance Day (United Kingdom) |
E779431
|
entity |
| Predicate | traditionalSilenceTime |
P195903
|
FINISHED |
| Object | 11:00 |
—
|
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: 11:00 | Statement: [Remembrance Day (United Kingdom), traditionalSilenceTime, 11:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSilenceTime Context triple: [Remembrance Day (United Kingdom), traditionalSilenceTime, 11:00]
-
A.
traditionalSilenceDuration
chosen
Indicates the length of time that silence is customarily observed in a given traditional or ritual context.
-
B.
typicalDelay
Indicates the usual or expected amount of time by which something is delayed relative to its planned or nominal schedule.
-
C.
timeOfDialogue
Indicates the specific time or temporal context at which a dialogue or conversational exchange occurs.
-
D.
isSilentExceptFor
Indicates that an entity produces no sound or noise except under specific conditions or in certain contexts.
-
E.
timeThreshold
Indicates a temporal limit or cutoff point after which a related condition, event, or state changes or no longer applies.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: April 29, 2026, 8:27 p.m.