Triple
T7365539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Assembly of Pakistan |
E169859
|
entity |
| Predicate | firstConstituted |
P23213
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [National Assembly of Pakistan, firstConstituted, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstConstituted Context triple: [National Assembly of Pakistan, firstConstituted, 1947]
-
A.
firstConstitutedIn
chosen
Indicates the time or context in which an entity (such as an organization, body, or structure) was originally formed or formally established.
-
B.
earliestConstitutionAdopted
Indicates that one entity is the constitution that was adopted first in time among all constitutions associated with another entity.
-
C.
firstCongressDate
Indicates the calendar date on which the first congress or formal assembly associated with an entity took place.
-
D.
firstConstitutionalElectionsHeld
Indicates that the first elections conducted under a new or newly adopted constitution have taken place.
-
E.
servedAsConstitutionUntil
Indicates that one document functioned as the official constitution of an entity up to a specified point in time.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.