Triple

T37186154
Position Surface form Disambiguated ID Type / Status
Subject Pantalica archaeological area E921325 entity
Predicate hasNecropolisName P107125 FINISHED
Object South Necropolis
South Necropolis is one of the major rock-cut burial complexes within the ancient Pantalica archaeological site in southeastern Sicily.
E2219744 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: South Necropolis | Statement: [Pantalica archaeological area, hasNecropolisName, South Necropolis]
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: South Necropolis
Triple: [Pantalica archaeological area, hasNecropolisName, South Necropolis]
Generated description
South Necropolis is one of the major rock-cut burial complexes within the ancient Pantalica archaeological site in southeastern Sicily.

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_69f76ea250bc819083f28d81de25cd0c completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a008cedfffc8190a468423633d523df completed May 10, 2026, 1:49 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4043b2801881908e14c2458bc9c998 completed June 27, 2026, 9:42 p.m.
NEDg Description generation batch_6a404792df948190864c86e7408c60e1 completed June 27, 2026, 9:58 p.m.
NED2 Entity disambiguation (via description) batch_6a4047ee10b48190a0fb36850efe09bb completed June 27, 2026, 10 p.m.
Created at: May 3, 2026, 4:15 p.m.