Triple
T21998135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IES/ISS Examination |
E543256
|
entity |
| Predicate | locationOfConduct |
P65992
|
FINISHED |
| Object | various centres across India |
—
|
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: various centres across India | Statement: [IES/ISS Examination, locationOfConduct, various centres across India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfConduct Context triple: [IES/ISS Examination, locationOfConduct, various centres across India]
-
A.
locationOfEventDescribed
Indicates that one entity is the place or setting where the event described by another entity occurs.
-
B.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
-
C.
operationLocation
chosen
Indicates the place or site where an operation, activity, or process is carried out.
-
D.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
E.
defendantLocation
Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276774508190b96870266e10979a |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.