Triple
T4865789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokhchi |
E108765
|
entity |
| Predicate | returnFromExile |
P32432
|
FINISHED |
| Object | late 1950s |
—
|
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: late 1950s | Statement: [Nokhchi, returnFromExile, late 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnFromExile Context triple: [Nokhchi, returnFromExile, late 1950s]
-
A.
returnedFromExile
chosen
Indicates that an entity has come back to its original place or community after a period of being exiled.
-
B.
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.
-
C.
exileLocation
Indicates the place or destination to which an entity is sent or kept in exile.
-
D.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
E.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d7861e88190ad172632eb5507c7 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.