Triple
T8932490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Americo-Liberian settlers |
E212690
|
entity |
| Predicate | beganMigration |
P19545
|
FINISHED |
| Object | 1820 |
—
|
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: 1820 | Statement: [Americo-Liberian settlers, beganMigration, 1820]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganMigration Context triple: [Americo-Liberian settlers, beganMigration, 1820]
-
A.
migrationBeganApprox
Indicates that the start of a migration occurred around an estimated time rather than at a precisely known moment.
-
B.
enabledMigrationOf
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
C.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
D.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
E.
migrationBackground
Indicates that an entity has a personal or familial history of moving from one country or region to another, typically across national borders.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668e5c108190b08f9cd6b4fd4a8b |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.