Triple
T25313136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesfeier |
E634659
|
entity |
| Predicate | hasDateNotation |
P44879
|
FINISHED |
| Object | 1. August |
—
|
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: 1. August | Statement: [Bundesfeier, hasDateNotation, 1. August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateNotation Context triple: [Bundesfeier, hasDateNotation, 1. August]
-
A.
dateNotation
chosen
Indicates how a date is written or formatted in notation (e.g., order and style of day, month, and year).
-
B.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
C.
hasDateContext
Indicates that something is associated with, constrained by, or interpreted within a specific date or time-related context.
-
D.
hasSymbolicDate
Indicates that an entity is associated with a date that carries symbolic, commemorative, or representational significance beyond its literal calendar value.
-
E.
hasVariableDate
Indicates that the associated date is not fixed but can change or vary depending on conditions or context.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:27 p.m.