Triple
T24970775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mansur Rajih |
E624881
|
entity |
| Predicate | contextOfRecognition |
P36
|
FINISHED |
| Object | exile |
—
|
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: exile | Statement: [Mansur Rajih, contextOfRecognition, exile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contextOfRecognition Context triple: [Mansur Rajih, contextOfRecognition, exile]
-
A.
contextOf
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
B.
regionOfRecognition
Indicates the geographic or administrative area within which something is officially acknowledged, valid, or recognized.
-
C.
context
chosen
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
D.
acquisitionContext
Indicates the circumstances, conditions, or setting under which an acquisition or purchase takes place.
-
E.
currentRecognition
Indicates the recognition or acknowledgment an entity presently receives, such as awards, honors, or formal status it currently holds.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:01 a.m.