Triple
T4053806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sailendra dynasty |
E84645
|
entity |
| Predicate | possibleMigration |
P46679
|
FINISHED |
| Object | to Srivijaya in Sumatra |
—
|
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: to Srivijaya in Sumatra | Statement: [Sailendra dynasty, possibleMigration, to Srivijaya in Sumatra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleMigration Context triple: [Sailendra dynasty, possibleMigration, to Srivijaya in Sumatra]
-
A.
enabledMigrationOf
Indicates that one entity made it possible for another entity to move, transfer, or transition from one state, location, or system to another.
-
B.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
C.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
D.
migrationCause
Indicates the reason or driving factor that leads an entity to migrate from one place to another.
-
E.
mayRelocateTo
chosen
Indicates that an entity has the possibility or permission to move or be moved from its current location to another specified location.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.