Triple
T25489131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gonobhaban |
E638791
|
entity |
| Predicate | namedAfterLanguageWord |
P63
|
FINISHED |
| Object | Bangla word "Gono" meaning "people" |
—
|
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: Bangla word "Gono" meaning "people" | Statement: [Gonobhaban, namedAfterLanguageWord, Bangla word "Gono" meaning "people"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterLanguageWord Context triple: [Gonobhaban, namedAfterLanguageWord, Bangla word "Gono" meaning "people"]
-
A.
namedAfter
chosen
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
B.
namedForPortmanteauOf
Indicates that something is named using a portmanteau formed by blending parts of two or more other names or words.
-
C.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
D.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
-
E.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 2:34 p.m.