Triple
T7147904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic Party presidential primaries, 2004 |
E166614
|
entity |
| Predicate | conventionEndDate |
P140
|
FINISHED |
| Object | 2004-07-29 |
—
|
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: 2004-07-29 | Statement: [Democratic Party presidential primaries, 2004, conventionEndDate, 2004-07-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conventionEndDate Context triple: [Democratic Party presidential primaries, 2004, conventionEndDate, 2004-07-29]
-
A.
conventionAdoptedAt
Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
-
B.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
associatedConvention
Indicates a relationship where something is linked or connected to a particular convention (such as an event, standard, or formal gathering).
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d6313c8190bdd34e700fc65502 |
completed | March 27, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.