Triple
T1397202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baba-e-Qaum |
E30693
|
entity |
| Predicate | honorificForRole |
P2097
|
FINISHED |
| Object | founder of Pakistan |
—
|
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: founder of Pakistan | Statement: [Baba-e-Qaum, honorificForRole, founder of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificForRole Context triple: [Baba-e-Qaum, honorificForRole, founder of Pakistan]
-
A.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
B.
honorificDescription
Indicates that one entity is described using an honorific or respectful title or phrase referring to another entity.
-
C.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
D.
honorificTitle
chosen
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
E.
honorificNickname
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3817320819093067b1444d70b74 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.