Triple

T31545448
Position Surface form Disambiguated ID Type / Status
Subject Luristan E804859 entity
Predicate hasProvinceSuccessor P123680 FINISHED
Object Lorestan Province NE NERFINISHED

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: Lorestan Province | Statement: [Luristan, hasProvinceSuccessor, Lorestan Province]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProvinceSuccessor
Context triple: [Luristan, hasProvinceSuccessor, Lorestan Province]
  • A. successorProvinceOrState chosen
    Indicates that one province or state has officially replaced or continued the role of another as its successor.
  • B. hasCitySuccessor
    Indicates that one city is the successor or replacement of another city, typically in terms of status, function, or administrative role.
  • C. hasSubdivisionSuccessor
    Indicates that one administrative or territorial subdivision directly succeeds another in an ordered sequence or historical progression.
  • D. hasProvinceEquivalent
    Indicates that one administrative division is equivalent in status or function to a province within a given political or territorial system.
  • E. successorTerritorialEntity
    Indicates that one territorial entity directly follows and replaces another in governing authority or jurisdiction over a given area.
  • 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_69f348d11a048190a65eb8384a3754ac completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a00717f539c8190b70dd0e72c6f7d24 completed May 10, 2026, 11:52 a.m.
PD Predicate disambiguation batch_6a00710278fc81908889afdcf459ff01 completed May 10, 2026, 11:50 a.m.
Created at: April 30, 2026, 10:08 p.m.