Triple
T284652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romulus Augustulus |
E5861
|
entity |
| Predicate | afterDepositionStatus |
P4339
|
FINISHED |
| Object | lived in retirement |
—
|
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: lived in retirement | Statement: [Romulus Augustulus, afterDepositionStatus, lived in retirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterDepositionStatus Context triple: [Romulus Augustulus, afterDepositionStatus, lived in retirement]
-
A.
finalDisposition
chosen
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
B.
deposedBy
Indicates that an entity has been removed from a position of power or authority by another entity.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
E.
reassessedAfter
Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.