Triple
T697239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsis |
E13919
|
entity |
| Predicate | migrationPeriod |
P12621
|
FINISHED |
| Object | early medieval period |
—
|
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: early medieval period | Statement: [Parsis, migrationPeriod, early medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationPeriod Context triple: [Parsis, migrationPeriod, early medieval period]
-
A.
notableMigrationPeriod
chosen
Indicates a period of time during which a significant or historically important migration event occurred.
-
B.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
C.
migrationEvent
Indicates an event in which one or more entities move or relocate from one place or context to another, typically across defined boundaries or regions.
-
D.
migrationPattern
Indicates the typical routes, timing, and destinations followed by entities as they move periodically from one location or region to another.
-
E.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.