Triple
T11766343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second All-Russian Congress of Soviets |
E279790
|
entity |
| Predicate | startDateOldStyle |
P23455
|
FINISHED |
| Object | 1917-10-25 |
—
|
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: 1917-10-25 | Statement: [Second All-Russian Congress of Soviets, startDateOldStyle, 1917-10-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateOldStyle Context triple: [Second All-Russian Congress of Soviets, startDateOldStyle, 1917-10-25]
-
A.
dateOldStyle
chosen
Indicates that a given date is expressed using the Old Style (Julian calendar) rather than the New Style (Gregorian calendar) convention.
-
B.
birthDateOldStyle
Indicates that an entity’s birth date is recorded according to an older or superseded calendar or dating system (e.g., Julian vs. Gregorian).
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
startDateAsGuerrilla
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
-
E.
formerFixedDate
Indicates that a previously established specific date associated with an event or relationship has changed and is no longer current.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:41 p.m.