Triple

T23708408
Position Surface form Disambiguated ID Type / Status
Subject Jan Amor Tarnowski E585793 entity
Predicate positionHeld P8 FINISHED
Object Starost of Czorsztyn
The Starost of Czorsztyn was a royal administrative and judicial official overseeing the Czorsztyn region and its castle in the Kingdom of Poland.
E1624190 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: Starost of Czorsztyn | Statement: [Jan Amor Tarnowski, positionHeld, Starost of Czorsztyn]
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: Starost of Czorsztyn
Triple: [Jan Amor Tarnowski, positionHeld, Starost of Czorsztyn]
Generated description
The Starost of Czorsztyn was a royal administrative and judicial official overseeing the Czorsztyn region and its castle in the Kingdom of Poland.

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_69e24905f77881908194d645676acd60 completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b775a4288190bbee7bd4b5bbcd75 completed April 29, 2026, 7:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fbce5b91481909f20b59b8f8e6e7f completed May 22, 2026, 2:18 a.m.
NEDg Description generation batch_6a0fbe20f8a08190ba69e7522ab90ae9 completed May 22, 2026, 2:23 a.m.
NED2 Entity disambiguation (via description) batch_6a0fbe91ec308190a12d563b9c15edaa completed May 22, 2026, 2:25 a.m.
Created at: April 17, 2026, 6:53 p.m.