Triple
T20818765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel Massoud Amir Behrani |
E512513
|
entity |
| Predicate | postImmigrationJob |
P141951
|
FINISHED |
| Object | roadside laborer |
—
|
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: roadside laborer | Statement: [Colonel Massoud Amir Behrani, postImmigrationJob, roadside laborer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postImmigrationJob Context triple: [Colonel Massoud Amir Behrani, postImmigrationJob, roadside laborer]
-
A.
postOccupationIssue
Indicates that an issue or problem arises or is identified after an occupation, role, or position has ended.
-
B.
immigrationBackground
Indicates that an entity has a personal or familial history of migration from another country or region.
-
C.
immigrationType
Indicates the specific category or classification of an individual’s immigration status or entry into a country.
-
D.
reportsToImmigration
Indicates that one entity formally provides information, updates, or declarations to an immigration authority or system.
-
E.
employmentAction
Indicates an action or event that changes, initiates, or terminates an employment relationship between entities.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f5b1e08190a9c26f76bd544b68 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:41 p.m.