Triple
T27491167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. House of Representatives elections in Oregon |
E693887
|
entity |
| Predicate | heldOnDayPattern |
P9394
|
FINISHED |
| Object | Tuesday following the first Monday in November |
—
|
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: Tuesday following the first Monday in November | Statement: [U.S. House of Representatives elections in Oregon, heldOnDayPattern, Tuesday following the first Monday in November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOnDayPattern Context triple: [U.S. House of Representatives elections in Oregon, heldOnDayPattern, Tuesday following the first Monday in November]
-
A.
heldOnDayOfWeek
Indicates that an event or activity takes place on a specified day of the week.
-
B.
heldOn
chosen
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
C.
airedOnDay
Indicates that an event or program was broadcast on a specific day.
-
D.
heldOnSameDayAs
Indicates that two events or occurrences took place on the same calendar day.
-
E.
heldWhen
Indicates that a particular state, condition, or relationship was true during a specified time or under certain temporal circumstances.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e8941e081908e2b8e35bd5461cb |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:05 p.m.