Triple

T37498488
Position Surface form Disambiguated ID Type / Status
Subject Taybad E931894 entity
Predicate locatedInAdministrativeTerritory P40 FINISHED
Object Taybad County
Taybad County is an administrative division in Razavi Khorasan Province in northeastern Iran, centered around the city of Taybad near the Afghan border.
E2246331 NE 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: Taybad County | Statement: [Taybad, locatedInAdministrativeTerritory, Taybad County]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Taybad County
Triple: [Taybad, locatedInAdministrativeTerritory, Taybad County]
Generated description
Taybad County is an administrative division in Razavi Khorasan Province in northeastern Iran, centered around the city of Taybad near the Afghan border.

Provenance (5 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_69f76ec457a4819094eeb3aed9baac11 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba382bb60819083b5dd86df0c4322 completed May 6, 2026, 8:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410404dfc48190ba23edd95e5a8b3f completed June 28, 2026, 11:22 a.m.
NEDg Description generation batch_6a41049bdc7881908ffafe3ffbb24b99 completed June 28, 2026, 11:25 a.m.
NED2 Entity disambiguation (via description) batch_6a41059ef42c81909a94722a1563fcd1 completed June 28, 2026, 11:29 a.m.
Created at: May 3, 2026, 4:17 p.m.