Triple

T31959066
Position Surface form Disambiguated ID Type / Status
Subject Ianus Patulcius E815984 entity
Predicate hasCounterpart P6587 FINISHED
Object Ianus Clusivius
Ianus Clusivius is a lesser-known aspect of the Roman god Janus, representing the closed or inward-facing phase in contrast to his open, outward-facing counterpart.
E850490 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: Ianus Clusivius | Statement: [Ianus Patulcius, hasCounterpart, Ianus Clusivius]
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: Ianus Clusivius
Triple: [Ianus Patulcius, hasCounterpart, Ianus Clusivius]
Generated description
Ianus Clusivius is a lesser-known aspect of the Roman god Janus, representing the closed or inward-facing phase in contrast to his open, outward-facing counterpart.

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_69f348f4ec708190abbb2a7c3ed58844 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b2b1de00819083a9d5654452e4cd completed May 3, 2026, 2:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34703015988190842130e92024d920 completed June 18, 2026, 10:24 p.m.
NEDg Description generation batch_6a34746da0f08190b7668348948d1b78 completed June 18, 2026, 10:42 p.m.
NED2 Entity disambiguation (via description) batch_6a34752cbca88190a23836df888e4e1a completed June 18, 2026, 10:46 p.m.
Created at: May 1, 2026, 12:08 a.m.