Triple
T11204714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipovans |
E265130
|
entity |
| Predicate | historicalPeriodOfMigration |
P80942
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Lipovans, historicalPeriodOfMigration, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfMigration Context triple: [Lipovans, historicalPeriodOfMigration, 17th century]
-
A.
historicalPopulationMovement
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
-
B.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
C.
historicalMigrationPeriodStart
Indicates the point in time when a particular historical migration period begins.
-
D.
majorImmigrationPeriod
Indicates that a time interval represents a significant period during which substantial immigration occurred.
-
E.
centuryOfMajorMigration
chosen
Indicates the century during which a major migration event involving the entity took place.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d355c481908fc3d555b596314d |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.