Triple
T4514467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Emergency (1975–1977) |
E102121
|
entity |
| Predicate | involvedArrestsOf |
P22280
|
FINISHED |
| Object | opposition leaders |
—
|
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: opposition leaders | Statement: [Indian Emergency (1975–1977), involvedArrestsOf, opposition leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedArrestsOf Context triple: [Indian Emergency (1975–1977), involvedArrestsOf, opposition leaders]
-
A.
arrests
chosen
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
-
B.
numberOfArrests
Indicates the count of times an entity has been arrested.
-
C.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
D.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
-
E.
formerlyInvolved
Indicates that an entity previously participated in or was associated with another entity or activity, but is no longer involved.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd572402f481908151f7899bc96306 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:02 p.m.