Triple
T29518285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Australia policy |
E748860
|
entity |
| Predicate | phasedOutDuring |
P162723
|
FINISHED |
| Object | post-World War II period |
—
|
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: post-World War II period | Statement: [White Australia policy, phasedOutDuring, post-World War II period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phasedOutDuring Context triple: [White Australia policy, phasedOutDuring, post-World War II period]
-
A.
graduallyPhasedOutIn
chosen
Indicates that something is discontinued or removed in a particular context or period through a slow, step-by-step process rather than all at once.
-
B.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
C.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
D.
decommissionedInPeriod
Indicates that an entity was formally taken out of service or use during a specified time period.
-
E.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c65323c81909ea69757d4d77bd0 |
completed | May 2, 2026, 9:28 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:39 p.m.