Triple
T28920882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minidoka National Historic Site |
E733507
|
entity |
| Predicate | operatedByDuringWar |
P126869
|
FINISHED |
| Object | War Relocation Authority |
—
|
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: War Relocation Authority | Statement: [Minidoka National Historic Site, operatedByDuringWar, War Relocation Authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByDuringWar Context triple: [Minidoka National Historic Site, operatedByDuringWar, War Relocation Authority]
-
A.
operatorDuringWorldWarII
chosen
Indicates that an entity operated or was active in its role during the period of World War II.
-
B.
ownerDuringWorldWarII
Indicates that one entity was the owner of another entity specifically during the time period of World War II.
-
C.
controlledByDuringWorldWarII
Indicates that one entity exercised political, military, or administrative control over another entity specifically during the period of World War II.
-
D.
wasOccupiedDuringWar
Indicates that a place or territory was under military or foreign control for some period during a specified war.
-
E.
enemyDuringWWII
Indicates that one entity was an enemy of the other during World War II.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: April 28, 2026, 8:19 a.m.