Triple

T34957375
Position Surface form Disambiguated ID Type / Status
Subject Miral Paris E1008154 entity
Predicate fatherFullName P16971 FINISHED
Object Thomas Eugene Paris
Thomas Eugene Paris is a fictional Starfleet officer and former convict who serves as the helmsman of the USS Voyager in the television series "Star Trek: Voyager."
E2119359 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: Thomas Eugene Paris | Statement: [Miral Paris, fatherFullName, Thomas Eugene Paris]
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: Thomas Eugene Paris
Triple: [Miral Paris, fatherFullName, Thomas Eugene Paris]
Generated description
Thomas Eugene Paris is a fictional Starfleet officer and former convict who serves as the helmsman of the USS Voyager in the television series "Star Trek: Voyager."

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_69f76dc69564819099e9e78aed6ff0a6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f7841dc4148190b04c5fbcd0d82ff8 completed May 3, 2026, 5:21 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37a8ce4e0881909578bc67acb0ef51 completed June 21, 2026, 9:03 a.m.
NEDg Description generation batch_6a37a9a50f1c819085a8f3c03b11a415 completed June 21, 2026, 9:06 a.m.
NED2 Entity disambiguation (via description) batch_6a37ab6826d48190a95fcf8f2b40186a completed June 21, 2026, 9:14 a.m.
Created at: May 3, 2026, 4 p.m.