Triple
T10531846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binoy |
E248460
|
entity |
| Predicate | workExplores |
P94403
|
FINISHED |
| Object | religious identity in colonial India |
—
|
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: religious identity in colonial India | Statement: [Binoy, workExplores, religious identity in colonial India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workExplores Context triple: [Binoy, workExplores, religious identity in colonial India]
-
A.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
B.
appliedWork
Indicates that an entity has put effort, skill, or labor into performing or producing a particular work or task.
-
C.
careerWalks
Indicates the total number of bases on balls (walks) a player has received over the course of their entire career.
-
D.
recommendedExperience
Indicates that a certain level or type of prior experience is advised or preferred for engaging in the related activity, role, or item.
-
E.
workIncludes
Indicates that a work (such as a project, document, or creative piece) contains or incorporates another specified component, part, or element.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:30 p.m.