Triple
T25313647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rütli meadow |
E634672
|
entity |
| Predicate | traditionalDateOfEvent |
P31438
|
FINISHED |
| Object | 1 August 1291 |
—
|
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 1291 | Statement: [Rütli meadow, traditionalDateOfEvent, 1 August 1291]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalDateOfEvent Context triple: [Rütli meadow, traditionalDateOfEvent, 1 August 1291]
-
A.
traditionalDateInJapan
Indicates that an entity has a specific date expressed in the traditional Japanese calendar system (e.g., era-based or lunisolar date).
-
B.
internationalDayDate
Indicates the calendar date on which a specific international day or observance is officially held each year.
-
C.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
D.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
E.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 21, 2026, 1:27 p.m.