Triple
T6983905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilquis Hyder |
E161913
|
entity |
| Predicate | workAuthorNationalityContext |
P6689
|
FINISHED |
| Object | British-Indian |
—
|
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: British-Indian | Statement: [Bilquis Hyder, workAuthorNationalityContext, British-Indian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAuthorNationalityContext Context triple: [Bilquis Hyder, workAuthorNationalityContext, British-Indian]
-
A.
authorNationality
chosen
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
B.
coAuthorNationality
Indicates that two or more co-authors of a work share the same nationality or have nationalities being related in the context of their co-authorship.
-
C.
creatorNationality
Indicates that the creator of an entity has a specified national affiliation or citizenship.
-
D.
literaryOriginCountry
Indicates the country from which a literary work or literary tradition originally comes.
-
E.
notableNationalityContext
Indicates that the subject’s nationality is notable or contextually relevant in relation to the associated entity or situation.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbbd926c8190a8b60527bd553fa3 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:31 p.m.