Triple
T27134469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asaka family |
E681642
|
entity |
| Predicate | lostOfficialStatusAfter |
P115064
|
FINISHED |
| Object | World War II |
—
|
NE NERFINISHED |
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: World War II | Statement: [Asaka family, lostOfficialStatusAfter, World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostOfficialStatusAfter Context triple: [Asaka family, lostOfficialStatusAfter, World War II]
-
A.
lostStatusConfirmedBy
Indicates that the confirmation or verification of an item’s lost status is provided or asserted by a specific agent or source.
-
B.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
C.
removedOfficialStatusFrom
Indicates that one entity revoked or took away the official status or position previously held by another entity.
-
D.
lostStatusReason
Indicates the reason or cause for which something transitioned into a lost or unsuccessful status.
-
E.
lostCapitalStatusUnder
chosen
Indicates that an entity ceased to hold its status as a capital under the authority, regime, or period specified by another entity.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62479bbb88190bcad383443cbd638 |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 9:06 a.m.