Triple
T8456344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raqeeb Se |
E199927
|
entity |
| Predicate | appreciatedBy |
P49305
|
FINISHED |
| Object | readers of Urdu literature worldwide |
—
|
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: readers of Urdu literature worldwide | Statement: [Raqeeb Se, appreciatedBy, readers of Urdu literature worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appreciatedBy Context triple: [Raqeeb Se, appreciatedBy, readers of Urdu literature worldwide]
-
A.
praisedEntity
chosen
Indicates that one entity expresses approval, admiration, or commendation toward another entity.
-
B.
creditedFor
Indicates that one entity is acknowledged as the source, contributor, or originator responsible for another entity (such as a work, achievement, or outcome).
-
C.
notablePraise
Indicates that one entity has given significant or distinguished praise or commendation to another entity.
-
D.
notableFavorite
Indicates that one entity is a particularly prominent or distinguished favorite of another entity compared to other possible favorites.
-
E.
liveFavoriteOf
Indicates that one entity is the preferred or most favored choice of another in a live or real-time context.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe48f180c8190a71cf9d7248ade60 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.