Triple
T20129763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanka |
E490856
|
entity |
| Predicate | exileType |
P138786
|
FINISHED |
| Object | 12 years in forest and 1 year incognito |
—
|
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: 12 years in forest and 1 year incognito | Statement: [Kanka, exileType, 12 years in forest and 1 year incognito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exileType Context triple: [Kanka, exileType, 12 years in forest and 1 year incognito]
-
A.
exileCountry
Indicates that an entity has been banished from or forced to live outside a specified country.
-
B.
exileEnd
Indicates the point or event at which a period of exile for an entity comes to an end.
-
C.
exileStart
Indicates the point in time or event when an entity begins being forced to live away from its home or native place.
-
D.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
E.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
- F. None of above. chosen
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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66760b8f08190a66fbb2e9e3925a3 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:31 p.m.