Triple

T32462290
Position Surface form Disambiguated ID Type / Status
Subject Vic E829607 entity
Predicate hasPart P35 FINISHED
Object Roman Temple of Vic
The Roman Temple of Vic is a well-preserved 2nd-century Roman temple in the Catalan city of Vic, Spain, notable for its classical architecture and later incorporation into medieval and modern structures.
E2007217 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: Roman Temple of Vic | Statement: [Vic, hasPart, Roman Temple of Vic]
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: Roman Temple of Vic
Triple: [Vic, hasPart, Roman Temple of Vic]
Generated description
The Roman Temple of Vic is a well-preserved 2nd-century Roman temple in the Catalan city of Vic, Spain, notable for its classical architecture and later incorporation into medieval and modern structures.

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_69f3491df9288190afc0b23b1d6e72ce completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c322957c8190806ebfc8a6647570 completed May 3, 2026, 3:38 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34669318088190b3068eca448173fb completed June 18, 2026, 9:43 p.m.
NEDg Description generation batch_6a34678a344c8190a37da291fe37b6d1 completed June 18, 2026, 9:47 p.m.
NED2 Entity disambiguation (via description) batch_6a34682ebe448190b88c760af0af9dfa completed June 18, 2026, 9:50 p.m.
Created at: May 1, 2026, 12:57 a.m.