Triple
T28329002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Tuesday Democratic primaries, 2024 |
E717486
|
entity |
| Predicate | isEventIn |
P19113
|
FINISHED |
| Object | 2020s in United States politics |
—
|
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: 2020s in United States politics | Statement: [Super Tuesday Democratic primaries, 2024, isEventIn, 2020s in United States politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEventIn Context triple: [Super Tuesday Democratic primaries, 2024, isEventIn, 2020s in United States politics]
-
A.
eventIn
chosen
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
B.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
C.
isPremierEventIn
Indicates that an event is recognized as the primary or most important event within a specified context, location, or series.
-
D.
isLinkedToEvent
Indicates that an entity has an association or connection with a specific event.
-
E.
isVenueWithin
Indicates that one venue is geographically located inside the boundaries or area of another place or region.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6493156c0819085e5d4796ce46b5a |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:30 a.m.