Triple
T37956888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohandas B.A.L.L.B. |
E946890
|
entity |
| Predicate | featuresProminentRoleBy |
P193877
|
FINISHED |
| Object | Pankaj Kapur |
E280419
|
NE 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: Pankaj Kapur | Statement: [Mohandas B.A.L.L.B., featuresProminentRoleBy, Pankaj Kapur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProminentRoleBy Context triple: [Mohandas B.A.L.L.B., featuresProminentRoleBy, Pankaj Kapur]
-
A.
featuresEarlyProminentRoleFor
Indicates that something includes another entity in an early and prominently visible or important role.
-
B.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
C.
featuresPeople
chosen
Indicates that something prominently includes or showcases specific people as part of its content or presentation.
-
D.
featuresResponseOfPeople
Indicates a relationship where something presents or includes the reactions, opinions, or feedback expressed by people.
-
E.
featuresLeader
Indicates that one entity includes, presents, or highlights another entity in the role of a leader.
- F. None of above.
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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a46b209b54881909c76c6422006fa5b |
completed | July 2, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.