Triple
T16973370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piyale Pasha |
E411743
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Pasha |
E163294
|
NE 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: Pasha | Statement: [Piyale Pasha, title, Pasha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pasha Context triple: [Piyale Pasha, title, Pasha]
-
A.
Pasha
chosen
Pasha is a high-ranking title of nobility and military or administrative authority historically used in the Ottoman Empire and some neighboring regions.
-
B.
Peshewa
Peshewa, also known as Jean Baptiste Richardville, was a prominent 19th-century Miami (Myaamia) chief influential in treaty negotiations with the United States in the Great Lakes region.
-
C.
Pasha Qasim
Pasha Qasim was an Ottoman military leader and provincial governor whose legacy is notably marked by the mosque bearing his name in Pécs, Hungary.
-
D.
Tagau Pashayi
Tagau Pashayi is a specific variety of the Pashayi languages spoken by Pashayi communities in eastern Afghanistan.
-
E.
Farhat
Farhat is a surname of Arabic origin borne by various individuals, including Tunisian figures such as Chadlia Saïda Farhat.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0af06688190a77682aa297cd27e |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d4738fbc819099e8281ebc777091 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:31 a.m.