Triple

T35040527
Position Surface form Disambiguated ID Type / Status
Subject New Nisa E1011056 entity
Predicate alsoKnownAs P39 FINISHED
Object Parthian Nisa
Parthian Nisa was an ancient city and early royal residence of the Parthian Empire, located near modern Ashgabat in present-day Turkmenistan and renowned for its archaeological remains.
E2121724 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: Parthian Nisa | Statement: [New Nisa, alsoKnownAs, Parthian Nisa]
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: Parthian Nisa
Triple: [New Nisa, alsoKnownAs, Parthian Nisa]
Generated description
Parthian Nisa was an ancient city and early royal residence of the Parthian Empire, located near modern Ashgabat in present-day Turkmenistan and renowned for its archaeological remains.

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_69f76dcea02c81908542a223f6d5059f completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f785921bd881908979cf85cb13c80a completed May 3, 2026, 5:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37bd2ee2148190aa944631428527a4 completed June 21, 2026, 10:30 a.m.
NEDg Description generation batch_6a37bdc0a6888190985637b707ad25bf completed June 21, 2026, 10:32 a.m.
NED2 Entity disambiguation (via description) batch_6a37be8fbfc08190bc356dbcbc0a1b5f completed June 21, 2026, 10:35 a.m.
Created at: May 3, 2026, 4:01 p.m.