Triple

T31306213
Position Surface form Disambiguated ID Type / Status
Subject Mississippian period E798341 entity
Predicate hasMajorSite P5003 FINISHED
Object Mound Bottom
Mound Bottom is a significant prehistoric Native American archaeological site in Tennessee, notable for its large earthen mounds and association with the Mississippian culture.
E1972621 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: Mound Bottom | Statement: [Mississippian period, hasMajorSite, Mound Bottom]
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: Mound Bottom
Triple: [Mississippian period, hasMajorSite, Mound Bottom]
Generated description
Mound Bottom is a significant prehistoric Native American archaeological site in Tennessee, notable for its large earthen mounds and association with the Mississippian culture.

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_69f224e0bd4c8190aab9b29a73f7aa3c completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69e6340b08190952da7e448346914 completed May 3, 2026, 1:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b849793bc81909e77da03a5c63483 completed June 12, 2026, 4:01 a.m.
NEDg Description generation batch_6a2b852366948190b8b8641fe28b1d81 completed June 12, 2026, 4:03 a.m.
NED2 Entity disambiguation (via description) batch_6a2b8598ebb481909235beb350564bce completed June 12, 2026, 4:05 a.m.
Created at: April 29, 2026, 9:14 p.m.