Triple
T31903420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zakiur Rehman Lakhvi |
E814482
|
entity |
| Predicate | hasBeenReleasedOn |
P181451
|
FINISHED |
| Object | bail in 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: bail in Pakistan | Statement: [Zakiur Rehman Lakhvi, hasBeenReleasedOn, bail in Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenReleasedOn Context triple: [Zakiur Rehman Lakhvi, hasBeenReleasedOn, bail in Pakistan]
-
A.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
B.
alsoReleasedOn
Indicates that the same item (such as a work, product, or release) was made available on an additional platform, format, or medium besides its primary one.
-
C.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
-
D.
hasReleaseMedium
Indicates the medium or format through which something (such as a work or product) is released or made available.
-
E.
alsoReleased
Indicates that two or more items were released at the same time or as part of the same release event.
- F. None of above. chosen
Provenance (4 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: May 1, 2026, midnight