Triple
T29077281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-23 |
E735975
|
entity |
| Predicate | tookMantleOf |
P96298
|
FINISHED |
| Object | Wolverine |
—
|
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: Wolverine | Statement: [X-23, tookMantleOf, Wolverine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookMantleOf Context triple: [X-23, tookMantleOf, Wolverine]
-
A.
takesOver
Indicates that one entity assumes control, ownership, or responsibility for another entity, often replacing its previous controller.
-
B.
tookThroneFollowing
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
-
C.
hasSuperheroMantle
chosen
Indicates that one entity holds or has assumed the superhero identity, title, or role associated with another entity.
-
D.
assumesDutiesOf
Indicates that one entity takes over and begins performing the responsibilities or role previously held by another entity.
-
E.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661407e5481908d8f224787f5f6be |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:23 a.m.