Triple
T25160982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKI |
E626436
|
entity |
| Predicate | re-emerged |
P82714
|
FINISHED |
| Object | post-World War II |
—
|
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: post-World War II | Statement: [PKI, re-emerged, post-World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: re-emerged Context triple: [PKI, re-emerged, post-World War II]
-
A.
reemergesAs
chosen
Indicates that an entity that previously disappeared, transformed, or became inactive later appears again in a new or altered form.
-
B.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
C.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
-
D.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
E.
recovered
Indicates that an entity has returned to a previous, healthier, normal, or functional state after a period of loss, damage, illness, or impairment.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b8d45548190a5bdb4fba1d3ba4e |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:31 a.m.