Triple
T8810462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial coronation journeys |
E209646
|
entity |
| Predicate | typicallyStartsAfter |
P32533
|
FINISHED |
| Object | election of the king of the Romans |
—
|
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: election of the king of the Romans | Statement: [Imperial coronation journeys, typicallyStartsAfter, election of the king of the Romans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyStartsAfter Context triple: [Imperial coronation journeys, typicallyStartsAfter, election of the king of the Romans]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
C.
typicalStartPeriod
chosen
Indicates the usual or standard time period during which something begins or is initiated.
-
D.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
E.
initiatedAfter
Indicates that one event or process begins only after another specified event or process has already started or occurred.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd69df4819091e9a7dad87265a4 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.