Triple
T3176648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurfürstenkollegium |
E66479
|
entity |
| Predicate | metFor |
P1220
|
FINISHED |
| Object | imperial elections |
—
|
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: imperial elections | Statement: [Kurfürstenkollegium, metFor, imperial elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metFor Context triple: [Kurfürstenkollegium, metFor, imperial elections]
-
A.
metOn
Indicates that two or more entities encountered each other at the same time and place for the first time or for a particular meeting.
-
B.
meets
chosen
Indicates that two or more entities come together at the same place and time, typically for interaction or a shared purpose.
-
C.
metBetween
Indicates that two or more entities had an in-person or virtual meeting or encounter with each other during a specified time or context.
-
D.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
-
E.
mustMeet
Indicates that one entity is required or obligated to have a meeting or encounter with another entity.
- 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_69ad8586a34c8190944c63ec11a8de1a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada69b0bec8190957913b44d876079 |
completed | March 8, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69ad9e02677c8190a21d93b1259b2761 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.