Triple
T18315581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tule Lake Segregation Center |
E438745
|
entity |
| Predicate | convertedToSegregationCenter |
P131306
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [Tule Lake Segregation Center, convertedToSegregationCenter, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedToSegregationCenter Context triple: [Tule Lake Segregation Center, convertedToSegregationCenter, 1943]
-
A.
segregatedIn
Indicates that one entity is separated or isolated within a specific space, group, or context defined by another entity.
-
B.
wasTransportedTo
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
-
C.
segregatedFor
Indicates that one entity is separated or set apart from others specifically for the use, benefit, or association of another entity.
-
D.
movedToDivision
Indicates that an entity has been transferred or reassigned from one division to another within an organization or structure.
-
E.
hadRegionalCenter
Indicates that an entity possessed, operated, or was associated with a specific regional center serving a defined geographic area.
- F. None of above. chosen
Provenance (4 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5021cc70c8190bf43bd75e4af7381 |
completed | April 19, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:36 a.m.