Triple
T37706758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Schedule of the Constitution of Pakistan |
E939217
|
entity |
| Predicate | oathFor |
P104641
|
FINISHED |
| Object | President of Pakistan |
—
|
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: President of Pakistan | Statement: [Second Schedule of the Constitution of Pakistan, oathFor, President of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathFor Context triple: [Second Schedule of the Constitution of Pakistan, oathFor, President of Pakistan]
-
A.
oath
Indicates a formal, binding promise or pledge made by one party to uphold certain duties, truths, or obligations, often under conditions of solemnity or authority.
-
B.
oathName
Indicates the specific name or title assigned to an oath in the relationship.
-
C.
hasOathTo
Indicates a relationship in which one entity is bound by an oath or sworn commitment to another entity.
-
D.
oathTakenBy
Indicates that an oath or formal promise has been made by a specific entity.
-
E.
oathsAbout
chosen
Indicates that one entity makes or concerns a formal oath regarding another entity or subject.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.