Triple

T30539919
Position Surface form Disambiguated ID Type / Status
Subject Thuburbo Maius E777245 entity
Predicate hasFeature P182 FINISHED
Object Temple of Peace
The Temple of Peace is an ancient Roman sanctuary located in the archaeological site of Thuburbo Maius in modern-day Tunisia, reflecting the city’s religious and civic life.
E1918714 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: Temple of Peace | Statement: [Thuburbo Maius, hasFeature, Temple of Peace]
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: Temple of Peace
Triple: [Thuburbo Maius, hasFeature, Temple of Peace]
Generated description
The Temple of Peace is an ancient Roman sanctuary located in the archaeological site of Thuburbo Maius in modern-day Tunisia, reflecting the city’s religious and civic life.

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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6888953688190ae6709934cc9fccd completed May 2, 2026, 11:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27be85f284819089f9e5aac8fcc1df completed June 9, 2026, 7:19 a.m.
NEDg Description generation batch_6a27bffda4a48190a42d2f3ae572738d completed June 9, 2026, 7:25 a.m.
NED2 Entity disambiguation (via description) batch_6a27c0660ba08190b19d482eaf3fac29 completed June 9, 2026, 7:27 a.m.
Created at: April 29, 2026, 8:19 p.m.