Triple
T24338451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amravati (Lok Sabha constituency) |
E613446
|
entity |
| Predicate | stateSince |
P76121
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Amravati (Lok Sabha constituency), stateSince, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateSince Context triple: [Amravati (Lok Sabha constituency), stateSince, 1962]
-
A.
inStateSince
chosen
Indicates that an entity has been in a particular state continuously starting from a specified point in time.
-
B.
knownSince
Indicates the point in time from which one entity has been aware of, acquainted with, or in possession of knowledge about another entity.
-
C.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
D.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
E.
controlledSince
Indicates that one entity has held control or authority over another entity starting from a specified point in time.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293225a58819082bba82ad445864f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.