Triple
T1758087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish diaspora |
E38594
|
entity |
| Predicate | peakMigrationPeriod |
P12621
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Irish diaspora, peakMigrationPeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakMigrationPeriod Context triple: [Irish diaspora, peakMigrationPeriod, 19th century]
-
A.
yearOfMajorMigration
Indicates the specific year in which a significant migration event involving the subject took place.
-
B.
notableMigrationPeriod
chosen
Indicates a period of time during which a significant or historically important migration event occurred.
-
C.
majorImmigrationPeriod
Indicates that a time interval represents a significant period during which substantial immigration occurred.
-
D.
establishedTransitionPeriod
Indicates that an entity has formally set or defined a specific transition period between two states, conditions, or arrangements.
-
E.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or 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_69a8862bdb2081908aefe831c8aa8017 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.