Triple
T822382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surendranath Banerjee |
E17777
|
entity |
| Predicate | reasonForEvent |
P20908
|
FINISHED |
| Object | dispute over age eligibility |
—
|
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: dispute over age eligibility | Statement: [Surendranath Banerjee, reasonForEvent, dispute over age eligibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEvent Context triple: [Surendranath Banerjee, reasonForEvent, dispute over age eligibility]
-
A.
reasonForChange
Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
-
B.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
C.
reasonForExecution
Indicates that one entity specifies the cause, motive, or justification for carrying out the execution of another entity or action.
-
D.
reasonWritten
Indicates that one entity is the reason or motivation for which another entity was written or authored.
-
E.
reasonForGrant
Indicates the justification, purpose, or cause for which a grant is awarded or provided.
- 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa76a7808190ac7fd9ba1a4cebcb |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab9634948190b25ea1b2e34df87d |
completed | March 1, 2026, 9:11 p.m. |
Created at: March 1, 2026, 7:38 p.m.