Triple
T15809284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian general elections |
E383302
|
entity |
| Predicate | canBeHeldEarlier |
P31218
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Indian general elections, canBeHeldEarlier, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeHeldEarlier Context triple: [Indian general elections, canBeHeldEarlier, yes]
-
A.
canBeHeldEarly
chosen
Indicates that an event, action, or process is allowed to occur earlier than its originally scheduled or typical time.
-
B.
canBeCalledEarlyBy
Indicates that one entity has the permission or capability to initiate an early call or invocation of another entity.
-
C.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
D.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
E.
notEarlierThan
Indicates that one event, time, or state does not occur before another, i.e., it is simultaneous with or later than the referenced point.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b529c6b481909664153ecc381f7c |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.