Triple

T24430979
Position Surface form Disambiguated ID Type / Status
Subject Commander Shepard E616000 entity
Predicate canRomance P154818 FINISHED
Object Jacob Taylor
Jacob Taylor is a human Alliance soldier and Cerberus operative who serves as a loyal squadmate and potential romantic partner for Commander Shepard in the Mass Effect video game series.
E1635354 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: Jacob Taylor | Statement: [Commander Shepard, canRomance, Jacob Taylor]
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: Jacob Taylor
Triple: [Commander Shepard, canRomance, Jacob Taylor]
Generated description
Jacob Taylor is a human Alliance soldier and Cerberus operative who serves as a loyal squadmate and potential romantic partner for Commander Shepard in the Mass Effect video game series.

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_69e2d7eadb248190a867130fe45f0388 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2a6d73e208190873ab97996fd6b28 completed April 30, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe3750a54819083bda5a3828bb0ed completed May 22, 2026, 5:02 a.m.
NEDg Description generation batch_6a0fe4f9f0448190bbd9e0b860335482 completed May 22, 2026, 5:09 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe620e40c81909973369ffb8e9dfc completed May 22, 2026, 5:14 a.m.
Created at: April 18, 2026, 2:16 a.m.