Triple
T11659514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totem of Undying |
E277086
|
entity |
| Predicate | regenerationDurationSeconds |
P98408
|
FINISHED |
| Object | 40 |
—
|
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: 40 | Statement: [Totem of Undying, regenerationDurationSeconds, 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regenerationDurationSeconds Context triple: [Totem of Undying, regenerationDurationSeconds, 40]
-
A.
regenerationOf
Indicates that one entity is the renewed, restored, or regrown version of another entity, typically after damage, loss, or degradation.
-
B.
regenerationStartedIn
Indicates that a regeneration process was initiated or began within a specified location, context, or time frame.
-
C.
hasRegenerationCycleWith
Indicates that two entities are linked by a recurring regeneration or renewal process that they undergo together or in relation to each other.
-
D.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
-
E.
recoveryDuration
chosen
Indicates the length of time required for an entity to return to a normal or functional state after an event, condition, or disruption.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.