Triple
T33772467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aftermath of World War II |
E865417
|
entity |
| Predicate | hasMajorProcess |
P1410
|
FINISHED |
| Object | postwar reconstruction |
—
|
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: postwar reconstruction | Statement: [aftermath of World War II, hasMajorProcess, postwar reconstruction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorProcess Context triple: [aftermath of World War II, hasMajorProcess, postwar reconstruction]
-
A.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
B.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
C.
hasMajorComponent
Indicates that one entity includes another entity as a primary or most significant component or part.
-
D.
hasMajorOutput
Indicates that an entity produces a primary or most significant output, result, or product.
-
E.
hasMajorWork
Indicates that an entity (typically a person, creator, or organization) is associated with a significant or principal work they produced or are best known for.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
Created at: May 1, 2026, 1:45 a.m.