Triple
T37344159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironton, Ohio |
E927125
|
entity |
| Predicate | holidayEvent |
P170336
|
FINISHED |
| Object | Memorial Day parade |
—
|
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: Memorial Day parade | Statement: [Ironton, Ohio, holidayEvent, Memorial Day parade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holidayEvent Context triple: [Ironton, Ohio, holidayEvent, Memorial Day parade]
-
A.
holidayType
Indicates the specific category or kind of holiday associated with an event or date (e.g., public, religious, national, or personal).
-
B.
holidayRole
Indicates the specific function, duty, or part an entity plays in relation to a holiday or holiday-related event.
-
C.
holidayAssociation
Indicates a relationship where one entity is connected to, themed around, or designated for a particular holiday.
-
D.
publicHolidayEvents
chosen
Indicates that certain events are designated to occur on or in connection with public holidays.
-
E.
ethnicHoliday
Indicates a holiday that is specifically associated with, celebrated by, or originating from a particular ethnic group.
- 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_69f76eb5e034819088e53ab5b7909a68 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.