Triple
T15603293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komnenian restoration |
E375087
|
entity |
| Predicate | startOfEvent |
P10624
|
FINISHED |
| Object | accession of Alexios I Komnenos |
—
|
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: accession of Alexios I Komnenos | Statement: [Komnenian restoration, startOfEvent, accession of Alexios I Komnenos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfEvent Context triple: [Komnenian restoration, startOfEvent, accession of Alexios I Komnenos]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
typeOfEventForStart
Indicates the specific kind or category of event that marks the beginning of something.
-
C.
allegedStartEvent
Indicates that an entity is claimed or reported (but not confirmed) to be the starting point or initiation of a particular event or process.
-
D.
eventStartDateOrganized
Indicates the date on which an event is formally scheduled or organized to begin.
-
E.
occasionForStart
chosen
Indicates that one event, condition, or circumstance serves as the trigger or reason for another event or process to begin.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e6399d88190b2c3e781667666d4 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.