Triple

T27811489
Position Surface form Disambiguated ID Type / Status
Subject Batuu E702528 entity
Predicate hasInhabitants P6481 FINISHED
Object Trandoshans
Trandoshans are a reptilian, warlike species from the Star Wars universe known for their hunting culture, regenerative abilities, and frequent work as mercenaries and bounty hunters.
E1791377 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: Trandoshans | Statement: [Batuu, hasInhabitants, Trandoshans]
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: Trandoshans
Triple: [Batuu, hasInhabitants, Trandoshans]
Generated description
Trandoshans are a reptilian, warlike species from the Star Wars universe known for their hunting culture, regenerative abilities, and frequent work as mercenaries and bounty hunters.

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_69ef840a16748190926719ab96120bae completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6383e63288190a7d5b06acef39665 completed May 2, 2026, 5:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12f71fd3748190816d74cdd9d942b7 completed May 24, 2026, 1:03 p.m.
NEDg Description generation batch_6a12f7ba8f048190ac484434da112aeb completed May 24, 2026, 1:06 p.m.
NED2 Entity disambiguation (via description) batch_6a12fbae881c8190a13234bf6ad26f8f completed May 24, 2026, 1:22 p.m.
Created at: April 27, 2026, 5:42 p.m.