Triple
T9840094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundhra scandal |
E239199
|
entity |
| Predicate | natureOfAllegation |
P873
|
FINISHED |
| Object | misuse of public funds |
—
|
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: misuse of public funds | Statement: [Mundhra scandal, natureOfAllegation, misuse of public funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfAllegation Context triple: [Mundhra scandal, natureOfAllegation, misuse of public funds]
-
A.
typeOfClaim
Indicates the specific category or nature of a claim being made in relation to an entity or statement.
-
B.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
C.
hasAllegationsOf
Indicates that one entity is accused or suspected of engaging in certain actions, behaviors, or misconduct, but without implying that these accusations are proven.
-
D.
allegedInjury
Indicates that an injury is claimed or asserted to have occurred, typically without being legally or factually established.
-
E.
accusationType
chosen
Indicates the specific category or nature of an accusation made by one party against another.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34b045481908f89abd576aab497 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.