Triple
T20934066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Skylitzes |
E515537
|
entity |
| Predicate | chronicleFocus |
P141739
|
FINISHED |
| Object | imperial politics |
—
|
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 politics | Statement: [John Skylitzes, chronicleFocus, imperial politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronicleFocus Context triple: [John Skylitzes, chronicleFocus, imperial politics]
-
A.
chronicleScope
Indicates the temporal or contextual span over which an event, process, or narrative is recorded or documented.
-
B.
chronologicallyFocusesOn
Indicates that something is primarily concerned with or organized around the sequence and progression of events over time.
-
C.
chronicledBy
Indicates that something is documented, recorded, or described in detail by a particular source, author, or record.
-
D.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
E.
chronologyOf
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
- F. None of above. chosen
Provenance (4 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f94fc194819099df82357a7f33c7 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:49 p.m.