Triple
T24235037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phocaeans |
E601850
|
entity |
| Predicate | migratedAfter |
P101191
|
FINISHED |
| Object | Persian conquest of Ionia |
—
|
NE NERFINISHED |
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: Persian conquest of Ionia | Statement: [Phocaeans, migratedAfter, Persian conquest of Ionia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migratedAfter Context triple: [Phocaeans, migratedAfter, Persian conquest of Ionia]
-
A.
establishedAfterMigrationFrom
Indicates that one entity was established only after another entity had migrated from a previous location or context.
-
B.
migratedAcross
Indicates movement of an entity from one side of a boundary, region, or area to the other, typically implying a significant relocation or crossing.
-
C.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
D.
relocatedAfter
chosen
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
E.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9a4b708190851504c302778fd2 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.