Triple
T25817138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joynagar Majilpur |
E650286
|
entity |
| Predicate | hasSweetSpeciality |
P17971
|
FINISHED |
| Object | Moa made with nolen gur |
—
|
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: Moa made with nolen gur | Statement: [Joynagar Majilpur, hasSweetSpeciality, Moa made with nolen gur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSweetSpeciality Context triple: [Joynagar Majilpur, hasSweetSpeciality, Moa made with nolen gur]
-
A.
hasSpecialtyFood
chosen
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
B.
hasDessert
Indicates that one entity is served, accompanied, or associated with a particular dessert item.
-
C.
hasSpecialIndulgence
Indicates that one entity grants or possesses a particular privilege, exemption, or favor specifically afforded to another entity.
-
D.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
-
E.
hasSpice
Indicates that one entity contains, includes, or is characterized by a particular spice or set of spices.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600ca169c8190b8f75d1d1e66396a |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:27 a.m.