Triple
T30239982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu al-Hasan al-Hashimi al-Qurashi |
E768882
|
entity |
| Predicate | claimedNisba |
P84454
|
FINISHED |
| Object | al-Qurashi |
—
|
NE NERFINISHED |
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: al-Qurashi | Statement: [Abu al-Hasan al-Hashimi al-Qurashi, claimedNisba, al-Qurashi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedNisba Context triple: [Abu al-Hasan al-Hashimi al-Qurashi, claimedNisba, al-Qurashi]
-
A.
usesNisba
Indicates that one entity forms or applies a nisba (a relational or adjectival form, often derived from a name or place) to or in relation to another entity.
-
B.
claimedAs
Indicates that one entity asserts ownership, authorship, responsibility, or some other form of association over another entity.
-
C.
usedNisba
chosen
Indicates that one entity is described or classified using a nisba (relational adjective or gentilic) derived from another entity.
-
D.
claimed
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
E.
claimedIn
Indicates that a statement, fact, or assertion is reported or documented within a particular source, document, or claim.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 7:38 p.m.