Triple
T4186152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airlangga |
E88315
|
entity |
| Predicate | afterAbdication |
P54523
|
FINISHED |
| Object | retired as a hermit |
—
|
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: retired as a hermit | Statement: [Airlangga, afterAbdication, retired as a hermit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterAbdication Context triple: [Airlangga, afterAbdication, retired as a hermit]
-
A.
abdicatingMonarch
Indicates a relationship where a monarch formally renounces or relinquishes their throne and ruling authority.
-
B.
abdicationStatus
Indicates the status of an entity’s formal renunciation or relinquishment of a position, role, or authority.
-
C.
abdicatedDuring
Indicates that a ruler or officeholder gave up their position or authority during a specified event or time period.
-
D.
abdicatedAt
Indicates the time or date at which an entity formally gave up or resigned from a position of authority or responsibility.
-
E.
abdicatedInFavorOf
Indicates that one entity has voluntarily renounced a position, role, or right so that another specific entity may assume it.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af04af4e44819098a9d7f91e65adf2 |
completed | March 9, 2026, 5:34 p.m. |
Created at: March 9, 2026, 3:45 p.m.