Triple
T5639700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sher-e-Bangla Nagar |
E124234
|
entity |
| Predicate | wasPlannedAs |
P50644
|
FINISHED |
| Object | new capital complex for East 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: new capital complex for East Pakistan | Statement: [Sher-e-Bangla Nagar, wasPlannedAs, new capital complex for East Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPlannedAs Context triple: [Sher-e-Bangla Nagar, wasPlannedAs, new capital complex for East Pakistan]
-
A.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
E.
originalPlan
chosen
Indicates that one entity is the initial or primary plan or intended course of action associated with 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022850bf08190953cd5394f821801 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.