Triple
T19559046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margraviate of Brandenburg |
E489392
|
entity |
| Predicate | electoralStatusStartTime |
P59525
|
FINISHED |
| Object | 1356 |
—
|
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: 1356 | Statement: [Margraviate of Brandenburg, electoralStatusStartTime, 1356]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralStatusStartTime Context triple: [Margraviate of Brandenburg, electoralStatusStartTime, 1356]
-
A.
endTimeOfElectoralStatus
Indicates the point in time at which a given electoral status or condition for an entity ceases to be in effect.
-
B.
startDateAsElectoralRegion
chosen
Indicates the date on which an entity first began to function or be recognized as an electoral region.
-
C.
candidacyStartDate
Indicates the date on which an entity’s candidacy for a role, position, or election officially begins.
-
D.
votingSystemStartDate
Indicates the date on which a particular voting system or method first began to be used or came into effect.
-
E.
electoralStatus
Indicates the current state or condition of an entity in relation to an election process (e.g., running, elected, defeated, or not a candidate).
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f723d5081909553a4363b579a6b |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.