Triple

T28029629
Position Surface form Disambiguated ID Type / Status
Subject West End (Portland, Maine) E708226 entity
Predicate hasLandmark P105 FINISHED
Object St. Louis Church (former)
St. Louis Church (former) is a historic former Catholic church building located in Portland, Maine’s West End neighborhood.
E1800655 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: St. Louis Church (former) | Statement: [West End (Portland, Maine), hasLandmark, St. Louis Church (former)]
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: St. Louis Church (former)
Triple: [West End (Portland, Maine), hasLandmark, St. Louis Church (former)]
Generated description
St. Louis Church (former) is a historic former Catholic church building located in Portland, Maine’s West End neighborhood.

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_69ef9b6bdd9c8190bb3a574a03774ad1 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f63c7164e48190a40df492718b3e3c completed May 2, 2026, 6:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b8ae216c8190bbb63e8f31be6ae2 completed May 26, 2026, 3:13 p.m.
NEDg Description generation batch_6a15bd928c9c8190aee388afd174809f completed May 26, 2026, 3:34 p.m.
NED2 Entity disambiguation (via description) batch_6a15be2646e08190984be11cae2f44b9 completed May 26, 2026, 3:37 p.m.
Created at: April 27, 2026, 8:15 p.m.