Triple

T36363925
Position Surface form Disambiguated ID Type / Status
Subject Church Street Graveyard, Mobile, Alabama E895567 entity
Predicate hasName P744 FINISHED
Object Church Street Graveyard
Church Street Graveyard is a historic cemetery in Mobile, Alabama, known for its 19th-century graves and significance to the city's early history.
E2182578 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: Church Street Graveyard | Statement: [Church Street Graveyard, Mobile, Alabama, hasName, Church Street Graveyard]
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: Church Street Graveyard
Triple: [Church Street Graveyard, Mobile, Alabama, hasName, Church Street Graveyard]
Generated description
Church Street Graveyard is a historic cemetery in Mobile, Alabama, known for its 19th-century graves and significance to the city's early history.

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_69f76e5044248190b390d8887dc03254 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7baeb258081909caac1a77e4e58ab completed May 3, 2026, 9:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39b42aca7881908c57bb20af974b29 completed June 22, 2026, 10:16 p.m.
NEDg Description generation batch_6a39b4cc15dc8190b6f8df04e6c47b62 completed June 22, 2026, 10:18 p.m.
NED2 Entity disambiguation (via description) batch_6a39b58fb8a88190853f5ed510ee6fa6 completed June 22, 2026, 10:22 p.m.
Created at: May 3, 2026, 4:10 p.m.