Triple
T1475979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Formosa |
E30841
|
entity |
| Predicate | statusAfterWorldWarII |
P5141
|
FINISHED |
| Object | placed under Republic of China administration |
—
|
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: placed under Republic of China administration | Statement: [Formosa, statusAfterWorldWarII, placed under Republic of China administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterWorldWarII Context triple: [Formosa, statusAfterWorldWarII, placed under Republic of China administration]
-
A.
statusAfterWWII
chosen
Indicates the condition, role, or classification an entity had following the end of World War II.
-
B.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
C.
statusDuringWorldWarII
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
D.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
E.
statusAfterColdWar
Indicates the condition or standing of an entity in the period following the end of the Cold War.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c602387c8190b97a20c8e05e3d16 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.