Triple

T35859480
Position Surface form Disambiguated ID Type / Status
Subject Ryloth E1036905 entity
Predicate government P2153 FINISHED
Object Ryloth government
The Ryloth government is the political authority of the Twi'lek homeworld in the Star Wars universe, overseeing the planet’s affairs amid frequent conflict and external control.
E2157902 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: Ryloth government | Statement: [Ryloth, government, Ryloth government]
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: Ryloth government
Triple: [Ryloth, government, Ryloth government]
Generated description
The Ryloth government is the political authority of the Twi'lek homeworld in the Star Wars universe, overseeing the planet’s affairs amid frequent conflict and external control.

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_69f76e1d279c8190843e5b64a0a12c3f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a97496a88190be5743c8dfbd7e0a completed May 3, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_6a389c3510308190b8109f8e670e0642 completed June 22, 2026, 2:21 a.m.
NEDg Description generation batch_6a389cfaa1fc81908e382b4befed99f6 completed June 22, 2026, 2:24 a.m.
NED2 Entity disambiguation (via description) batch_6a389d9dcbd88190b86408dcb14f8128 completed June 22, 2026, 2:27 a.m.
Created at: May 3, 2026, 4:06 p.m.