Triple
T26135695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naam Ghosa |
E659374
|
entity |
| Predicate | relatedTraditionFigure |
P68934
|
FINISHED |
| Object | Sankardev |
—
|
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: Sankardev | Statement: [Naam Ghosa, relatedTraditionFigure, Sankardev]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedTraditionFigure Context triple: [Naam Ghosa, relatedTraditionFigure, Sankardev]
-
A.
traditionAssociatesWith
Indicates that a particular tradition is connected or linked to another entity, such as a practice, group, place, or concept.
-
B.
linkedToTradition
chosen
Indicates a relationship where something is connected or related to a particular tradition, heritage, or customary practice.
-
C.
textBelongsToTradition
Indicates that a given text is associated with, derived from, or recognized as part of a particular intellectual, cultural, or religious tradition.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
variantTraditions
Indicates that there exist differing or alternative traditions or customary practices associated with the same subject or context.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 26, 2026, 8:17 p.m.