Triple

T26424412
Position Surface form Disambiguated ID Type / Status
Subject Mark Frauenfelder E664329 entity
Predicate givenName P17 FINISHED
Object Mark
Mark is a common masculine given name of Latin origin, derived from Marcus and historically associated with figures such as the evangelist Saint Mark.
E161211 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: Mark | Statement: [Mark Frauenfelder, givenName, Mark]
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: Mark
Triple: [Mark Frauenfelder, givenName, Mark]
Generated description
Mark is a common masculine given name of Latin origin, derived from Marcus and historically associated with figures such as the evangelist Saint Mark.

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_69ee883ad6a4819088f918e76122d690 completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f611b854b8819082ad4a3510a0eb65 completed May 2, 2026, 3:01 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11aec4a7dc8190a8e1e3fe1ea6d109 completed May 23, 2026, 1:42 p.m.
NEDg Description generation batch_6a11afe7f1f0819097ec0208368b6409 completed May 23, 2026, 1:47 p.m.
NED2 Entity disambiguation (via description) batch_6a11b0a521b08190bfda23906722482c completed May 23, 2026, 1:50 p.m.
Created at: April 26, 2026, 11:45 p.m.