Triple
T32509087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajak (MCU) |
E830879
|
entity |
| Predicate | givesLeadershipTo |
P39302
|
FINISHED |
| Object | Sersi (MCU) |
—
|
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: Sersi (MCU) | Statement: [Ajak (MCU), givesLeadershipTo, Sersi (MCU)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesLeadershipTo Context triple: [Ajak (MCU), givesLeadershipTo, Sersi (MCU)]
-
A.
followsLeadershipOf
Indicates that one entity accepts and acts under the guidance, direction, or authority of another entity’s leadership.
-
B.
assignsExecutivePowerTo
Indicates that executive authority or decision-making power is formally granted from one entity to another.
-
C.
surrenderedLeader
Indicates that an individual who held a leadership role has yielded or given up their position, authority, or control, typically in the context of defeat or submission.
-
D.
assumesDutiesOf
Indicates that one entity takes over and begins performing the responsibilities or role previously held by another entity.
-
E.
shiftedAuthorityTo
chosen
Indicates that decision-making power or control has been transferred from one entity to another.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.