Triple
T7310086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of Pakistan 1962 |
E168067
|
entity |
| Predicate | abrogatedIn |
P30300
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Constitution of Pakistan 1962, abrogatedIn, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abrogatedIn Context triple: [Constitution of Pakistan 1962, abrogatedIn, 1972]
-
A.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
-
B.
usedToAbrogate
Indicates that something served as the means or instrument by which a rule, law, agreement, or obligation was annulled, repealed, or rendered no longer valid.
-
C.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
D.
abolishedByDocument
Indicates that something (such as a law, rule, or institution) is formally ended, revoked, or nullified through the authority of a specific document.
-
E.
abolishedDuring
chosen
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebdbd6f481908e69e53dab452656 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.