Triple
T37978374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ofo language |
E947483
|
entity |
| Predicate | historicalMigrationArea |
P131659
|
FINISHED |
| Object | Ohio River Valley |
E49111
|
NE 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: Ohio River Valley | Statement: [Ofo language, historicalMigrationArea, Ohio River Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMigrationArea Context triple: [Ofo language, historicalMigrationArea, Ohio River Valley]
-
A.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
B.
historicalPopulationMovement
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
-
C.
historicalMigrationFactor
Indicates that the relationship or condition is influenced by patterns, causes, or consequences of past human migration.
-
D.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
E.
regionOfMigration
chosen
Indicates the geographic area from which an entity or population moves or migrates.
- F. None of above.
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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01d48f41f4819093a5b47288a073c1 |
completed | May 11, 2026, 1:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41542df4348190a6c671950caf8328 |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a01d3fa278c8190838174dd96ef5dde |
completed | May 11, 2026, 1:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.