Triple
T28072906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nishtar Park |
E709453
|
entity |
| Predicate | namedForPersonFullName |
P173372
|
FINISHED |
| Object | Sardar Abdur Rab Nishtar |
—
|
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: Sardar Abdur Rab Nishtar | Statement: [Nishtar Park, namedForPersonFullName, Sardar Abdur Rab Nishtar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForPersonFullName Context triple: [Nishtar Park, namedForPersonFullName, Sardar Abdur Rab Nishtar]
-
A.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
B.
namedForOrganization
Indicates that one entity bears a name that is derived from or given in honor of a particular organization.
-
C.
namedForPersonAffiliation
Indicates that something is named after a person specifically because of that person's affiliation with a particular group, organization, place, or role.
-
D.
namedPersonField
Indicates that a particular data field is designated to contain a person’s name.
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- F. None of above. chosen
Provenance (4 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 27, 2026, 8:47 p.m.