Triple
T23099974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom Zone |
E575997
|
entity |
| Predicate | timeEffect |
P48090
|
FINISHED |
| Object | reduced aging of prisoners |
—
|
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: reduced aging of prisoners | Statement: [Phantom Zone, timeEffect, reduced aging of prisoners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeEffect Context triple: [Phantom Zone, timeEffect, reduced aging of prisoners]
-
A.
temporalEffect
chosen
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
B.
timeOffsetEffect
Indicates how a change or offset in time influences or modifies the occurrence, state, or outcome of another event or process.
-
C.
effectDuration
Indicates the length of time for which an effect remains active or valid.
-
D.
timeDilationLevel
Indicates the degree to which time is experienced as slowed down or sped up for an entity relative to a reference frame.
-
E.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de81060819084ab618f05aae583 |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:58 p.m.