Triple
T10786756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitamarhi Lok Sabha constituency |
E254470
|
entity |
| Predicate | reservationFor |
P4923
|
FINISHED |
| Object | General |
—
|
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: General | Statement: [Sitamarhi Lok Sabha constituency, reservationFor, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationFor Context triple: [Sitamarhi Lok Sabha constituency, reservationFor, General]
-
A.
reservationIn
Indicates that a reservation is associated with, or booked for, a specific place, service, or resource.
-
B.
reservationProvision
Indicates that one entity provides, allocates, or sets aside a reservation (such as a booked resource, service slot, or capacity) for another entity.
-
C.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
D.
reservationEstablished
Indicates that a reservation has been successfully created and confirmed between the involved parties or systems.
-
E.
reservedFor
chosen
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d5422481908d7ab833c6cbc879 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.