Triple
T7049110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic primaries |
E163719
|
entity |
| Predicate | startTypically |
P32533
|
FINISHED |
| Object | early election year calendar |
—
|
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: early election year calendar | Statement: [Democratic primaries, startTypically, early election year calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTypically Context triple: [Democratic primaries, startTypically, early election year calendar]
-
A.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
B.
typicalStartPeriod
chosen
Indicates the usual or standard time period during which something begins or is initiated.
-
C.
traditionalStart
Indicates that an event, process, or sequence begins in the customary or historically established way.
-
D.
typicalGoing
Indicates that an entity is engaged in or undergoing a normal, expected instance of going or movement from one place to another.
-
E.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.