Triple
T1108404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rita Vrataski |
E25537
|
entity |
| Predicate | previousAbility |
P23409
|
FINISHED |
| Object | Mimic time-reset power (lost before main events of film) |
—
|
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: Mimic time-reset power (lost before main events of film) | Statement: [Rita Vrataski, previousAbility, Mimic time-reset power (lost before main events of film)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAbility Context triple: [Rita Vrataski, previousAbility, Mimic time-reset power (lost before main events of film)]
-
A.
previousMode
Indicates that one mode directly precedes another in a sequence or state transition.
-
B.
previousHome
Indicates that one entity served as a former or prior residence or home of another entity.
-
C.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
D.
previousRoute
Indicates that one route directly precedes another in an ordered sequence of routes.
-
E.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e6134481909f348986a25f65c6 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b749e2a881909ef28745a7d2d917 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b7bd3d50819091e6f1d2ffe4c7ee |
completed | March 1, 2026, 10:03 p.m. |
Created at: March 1, 2026, 7:43 p.m.