Triple
T33630055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madeiran Americans |
E861525
|
entity |
| Predicate | hasMigrationReason |
P134391
|
FINISHED |
| Object | economic opportunity |
—
|
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: economic opportunity | Statement: [Madeiran Americans, hasMigrationReason, economic opportunity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMigrationReason Context triple: [Madeiran Americans, hasMigrationReason, economic opportunity]
-
A.
hasReasonForMigration
chosen
Indicates that there exists a specific cause, motive, or justification for an entity’s act of migrating from one place to another.
-
B.
hasMigrationIssue
Indicates that an entity experiences a problem, error, or complication during a migration process from one system, environment, or version to another.
-
C.
hasMigrationTo
Indicates a directed movement or transfer from one place, system, or state to another.
-
D.
hasMigrationHistoryFrom
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
-
E.
hasMigrationDimension
Indicates that there exists a relevant aspect or factor of migration associated with the subject in relation to the object.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:41 a.m.