Triple
T4411910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Canadians |
E94869
|
entity |
| Predicate | mainEarlyOccupation |
P49040
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Japanese Canadians, mainEarlyOccupation, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEarlyOccupation Context triple: [Japanese Canadians, mainEarlyOccupation, fishing]
-
A.
earlyOccupation
chosen
Indicates that an entity held a particular occupation or job during an early stage of its life or career.
-
B.
earliestOccupation
Indicates that the associated occupation is the first or earliest known job or professional role held by the person in question.
-
C.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
D.
earliestOccupationDate
Indicates the earliest known date on which an entity began a particular occupation or role.
-
E.
traditionalOccupations
Indicates that an entity is associated with occupations or jobs that are customary, long-established, or culturally traditional within a particular community or context.
- 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.