Triple
T30894486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ava dynasty |
E786985
|
entity |
| Predicate | playedTransitionalRoleBetween |
P117492
|
FINISHED |
| Object | Pagan Kingdom |
—
|
NE NERFINISHED |
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: Pagan Kingdom | Statement: [Ava dynasty, playedTransitionalRoleBetween, Pagan Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedTransitionalRoleBetween Context triple: [Ava dynasty, playedTransitionalRoleBetween, Pagan Kingdom]
-
A.
hasPlayedRole
Indicates that an entity has performed or portrayed a particular role or character in some context (such as a film, play, or production).
-
B.
transitionedThrough
chosen
Indicates that an entity passed from one state, phase, or condition to another by way of an intermediate state, phase, or condition.
-
C.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
D.
carriedOutRole
Indicates that an entity performed or fulfilled a specific role in the context of an activity, event, or process.
-
E.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 8:49 p.m.