Triple
T36849813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professional Engineer (PE) (Pakistan) |
E910644
|
entity |
| Predicate | grantsPostNominal |
P1804
|
FINISHED |
| Object | PE |
—
|
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: PE | Statement: [Professional Engineer (PE) (Pakistan), grantsPostNominal, PE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsPostNominal Context triple: [Professional Engineer (PE) (Pakistan), grantsPostNominal, PE]
-
A.
equivalentEnglishPostNominal
Indicates that two post-nominal modifiers in English (elements following a noun) express the same meaning or function and can be treated as equivalent.
-
B.
hasPostnominalLetters
chosen
Indicates that a person holds specific postnominal letters (abbreviations after their name) signifying qualifications, honors, or titles.
-
C.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
-
D.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
E.
honoraryPrefix
Indicates that one entity serves as an honorific title or respectful prefix attached to the name of another entity.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:13 p.m.