Triple
T6522995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhimrao |
E151230
|
entity |
| Predicate | associatedWithPersonOccupation |
P35215
|
FINISHED |
| Object | jurist |
—
|
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: jurist | Statement: [Bhimrao, associatedWithPersonOccupation, jurist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPersonOccupation Context triple: [Bhimrao, associatedWithPersonOccupation, jurist]
-
A.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
B.
isAssociatedWithProfessionOfBearer
chosen
Indicates that one entity is connected to, or involved with, the profession or occupational role held by another entity.
-
C.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
D.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
-
E.
realPersonAffiliation
Indicates a relationship where a real person is formally associated or connected with an organization, group, or entity.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad970afc81909d3231203eacf413 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.