Triple
T23754903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bangabandhu Sheikh Mujibur Rahman Hall |
E587077
|
entity |
| Predicate | namedForTitleOfHonoree |
P39752
|
FINISHED |
| Object | Bangabandhu |
—
|
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: Bangabandhu | Statement: [Bangabandhu Sheikh Mujibur Rahman Hall, namedForTitleOfHonoree, Bangabandhu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForTitleOfHonoree Context triple: [Bangabandhu Sheikh Mujibur Rahman Hall, namedForTitleOfHonoree, Bangabandhu]
-
A.
namedForTitle
chosen
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with another entity.
-
B.
honoraryTitleGrantedTo
Indicates that an honorary title has been formally conferred upon a particular entity.
-
C.
namedForNotabilityOfHonoree
Indicates that something is named in recognition of the honoree’s notable achievements, status, or significance.
-
D.
namedInHonorBy
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
E.
honoreeGivenName
Indicates the given (first) name of a person who is being honored or recognized.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdab86108190becd7f27650082cc |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:14 p.m.