Triple

T28361055
Position Surface form Disambiguated ID Type / Status
Subject Tiruvuru (SC) E718362 entity
Predicate hasReservationStatusSince P199659 FINISHED
Object post-independence delimitation 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: post-independence delimitation | Statement: [Tiruvuru (SC), hasReservationStatusSince, post-independence delimitation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReservationStatusSince
Context triple: [Tiruvuru (SC), hasReservationStatusSince, post-independence delimitation]
  • A. hasReservationStatus
    Indicates that an entity is associated with a specific reservation and the current status or state of that reservation (e.g., pending, confirmed, canceled).
  • B. hasReservationIn
    Indicates that an entity holds or possesses a reservation at or within a specified place, service, or event.
  • C. hasReservationOf
    Indicates that one entity holds or possesses a reservation for another entity (such as a service, resource, or event).
  • D. hasReservationFor
    Indicates that an entity holds or is associated with a reservation for a specific event, service, or resource.
  • E. haveReservation
    Indicates that an entity holds or has made a reservation for a service, event, or resource.
  • F. None of above. chosen

Provenance (4 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_69eff6ed5af48190be4e0adf298223e0 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69ff4de66ba481908e7184b3cf9d4d2d completed May 9, 2026, 3:08 p.m.
PD Predicate disambiguation batch_69ff4c702a5881909c6684c74807e945 completed May 9, 2026, 3:02 p.m.
PDg Predicate description generation batch_69ff4de56fd48190aefdbf13c70f76ce completed May 9, 2026, 3:08 p.m.
Created at: April 28, 2026, 12:52 a.m.