Triple

T28656868
Position Surface form Disambiguated ID Type / Status
Subject Family 13 (Ferrar Group) E725356 entity
Predicate hasMember P10 FINISHED
Object Minuscule 1689
Minuscule 1689 is a Greek minuscule manuscript of the New Testament, notable as a member of the textual Family 13 (Ferrar Group) known for its distinctive variant readings.
E1836612 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: Minuscule 1689 | Statement: [Family 13 (Ferrar Group), hasMember, Minuscule 1689]
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: Minuscule 1689
Triple: [Family 13 (Ferrar Group), hasMember, Minuscule 1689]
Generated description
Minuscule 1689 is a Greek minuscule manuscript of the New Testament, notable as a member of the textual Family 13 (Ferrar Group) known for its distinctive variant readings.

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_69f01d84f5f0819087ab5e6143b14ed7 completed April 28, 2026, 2:37 a.m.
NER Named-entity recognition batch_69f652e891808190a31adc508777c3b2 completed May 2, 2026, 7:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a24bb89d7f48190a57088805d0100cc completed June 7, 2026, 12:30 a.m.
NEDg Description generation batch_6a24bfb0987c819089a6705bb5282c4e completed June 7, 2026, 12:47 a.m.
NED2 Entity disambiguation (via description) batch_6a24c54a5d648190b33935999d8f5f04 completed June 7, 2026, 1:11 a.m.
Created at: April 28, 2026, 4:55 a.m.