Triple

T867770
Position Surface form Disambiguated ID Type / Status
Subject IN-DL E18743 entity
Predicate subdivisionCategory P3599 FINISHED
Object union territory 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: union territory | Statement: [IN-DL, subdivisionCategory, union territory]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: subdivisionCategory
Context triple: [IN-DL, subdivisionCategory, union territory]
  • A. subdivisionRank chosen
    Indicates the hierarchical level or type of administrative or territorial subdivision that an entity occupies within a larger organizational or geographic structure.
  • B. subdivisionName1
    Indicates that the first named subdivision is identified by a specific name or designation within a larger geographic or organizational hierarchy.
  • C. hasSubdivision
    Indicates that one entity is divided into and contains another entity as one of its constituent parts or administrative units.
  • D. isResidentialSuburbOf
    Indicates that one area is a residential suburb that is part of or lies within the urban region of another area.
  • E. realEstateCategory
    Indicates the classification of a property into a specific type or category within real estate (e.g., residential, commercial, industrial).
  • 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_69a4938ce8688190a24bdfef82ba7d21 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac7e12b0819084d25b9a66888a91 completed March 1, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69a4aa87504481909618a6815948da6f completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.