Triple
T11095848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian administration of Nauru |
E262374
|
entity |
| Predicate | JapaneseOccupationPeriod |
P70035
|
FINISHED |
| Object | 1942–1945 |
—
|
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: 1942–1945 | Statement: [Australian administration of Nauru, JapaneseOccupationPeriod, 1942–1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JapaneseOccupationPeriod Context triple: [Australian administration of Nauru, JapaneseOccupationPeriod, 1942–1945]
-
A.
JapaneseOccupationStart
Indicates the point in time when a Japanese occupation of a place or population begins.
-
B.
wasUnderJapaneseControlUntil
chosen
Indicates that an entity was governed, occupied, or administered by Japan up to a specified end date or time period.
-
C.
statusDuringIndonesianOccupation
Indicates the condition or role an entity held specifically during the period of Indonesian occupation.
-
D.
administrativeStatusDuringJapaneseRule
Indicates the administrative status or classification an entity held under Japanese colonial rule during the specified period.
-
E.
preWarOccupation
Indicates the occupation or role a person held before a specific war or armed conflict.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0897188190b6c293b44990b3d4 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d7441aa3548190b92dbde57841c135 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.