Triple
T4411887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Brazilians |
E94868
|
entity |
| Predicate | returnMigrationTrend |
P5318
|
FINISHED |
| Object | dekasegi work in Japan |
—
|
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: dekasegi work in Japan | Statement: [Japanese Brazilians, returnMigrationTrend, dekasegi work in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnMigrationTrend Context triple: [Japanese Brazilians, returnMigrationTrend, dekasegi work in Japan]
-
A.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
B.
typicalMigrationStatus
Indicates the usual or characteristic migration state or pattern associated with an entity.
-
C.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
D.
migrationPolicy
Indicates the rules or strategies governing how entities move, transfer, or transition from one context, location, or state to another.
-
E.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b354e656dc819093ca8395d7334006 |
completed | March 13, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.