Triple
T17819579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippicus Bardanes |
E444939
|
entity |
| Predicate | deathAfterDeposition |
P129023
|
FINISHED |
| Object | shortly after 713 |
—
|
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: shortly after 713 | Statement: [Philippicus Bardanes, deathAfterDeposition, shortly after 713]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathAfterDeposition Context triple: [Philippicus Bardanes, deathAfterDeposition, shortly after 713]
-
A.
madeDyingDeposition
Indicates that an individual gave a formal statement or testimony while believing they were near death.
-
B.
afterDeathOf
Indicates that one event, state, or condition occurs subsequent to and as a result of the death of a specified entity.
-
C.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
D.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
E.
deathBefore
Indicates that one entity’s death occurred earlier in time than another entity’s death.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e489101aa48190a1439d8cb683bba9 |
completed | April 19, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:15 a.m.