Triple
T32293562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Gem |
E825028
|
entity |
| Predicate | effectScope |
P132368
|
FINISHED |
| Object | partial resurrection of a single person |
—
|
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: partial resurrection of a single person | Statement: [Phoenix Gem, effectScope, partial resurrection of a single person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectScope Context triple: [Phoenix Gem, effectScope, partial resurrection of a single person]
-
A.
impactScope
chosen
Indicates the extent or range within which an action, event, or entity produces effects or consequences.
-
B.
effectOnWorld
Indicates how an entity’s actions or existence change, influence, or impact the state of the world.
-
C.
existenceScope
Indicates the contextual or situational bounds within which an entity or condition is considered to exist or hold true.
-
D.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
E.
encodingScope
Indicates the range or extent of content or information that is covered, represented, or captured by a particular encoding.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 12:44 a.m.