Triple
T9971037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakata Gion Yamakasa |
E196203
|
entity |
| Predicate | startDateInYear |
P91368
|
FINISHED |
| Object | July 1 |
—
|
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: July 1 | Statement: [Hakata Gion Yamakasa, startDateInYear, July 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateInYear Context triple: [Hakata Gion Yamakasa, startDateInYear, July 1]
-
A.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
B.
contractStartYear
Indicates the calendar year in which a contract between parties officially begins.
-
C.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
D.
startDateAsGuerrilla
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
-
E.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
- F. None of above. chosen
Provenance (4 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b96b1c8190b9d3c1171346615a |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:48 p.m.