Triple
T9052773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War II aftermath in Asia |
E216924
|
entity |
| Predicate | hasMainAspect |
P30328
|
FINISHED |
| Object | decolonization in Asia |
—
|
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: decolonization in Asia | Statement: [World War II aftermath in Asia, hasMainAspect, decolonization in Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAspect Context triple: [World War II aftermath in Asia, hasMainAspect, decolonization in Asia]
-
A.
hasAspectSystem
Indicates that an entity possesses or is associated with a particular aspect system, such as a structured set of characteristics, dimensions, or perspectives.
-
B.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
-
C.
hasCanonicalAspect
Indicates that an entity is associated with its standard or officially recognized aspect, form, or representation.
-
D.
hasProminentAspect
chosen
Indicates that an entity possesses a particularly notable, dominant, or emphasized aspect or feature.
-
E.
hasMainPeriod
Indicates that something is associated with or characterized by a primary or most significant time period.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a71a9d88190949ef9dc6816d6ab |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.