Triple

T35565604
Position Surface form Disambiguated ID Type / Status
Subject Maryland Route 39 E1027763 entity
Predicate passesThrough P225 FINISHED
Object Crellin, Maryland
Crellin, Maryland is a small unincorporated community in Garrett County near the West Virginia border, historically tied to coal mining and the railroad.
E2287116 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: Crellin, Maryland | Statement: [Maryland Route 39, passesThrough, Crellin, Maryland]
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: Crellin, Maryland
Triple: [Maryland Route 39, passesThrough, Crellin, Maryland]
Generated description
Crellin, Maryland is a small unincorporated community in Garrett County near the West Virginia border, historically tied to coal mining and the railroad.

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_69f76e020fd8819081cb080e7e203083 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7987d08a08190b530a67af5735b1a completed May 3, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a47606a58348190b5f0f7ea58c99e62 completed July 3, 2026, 7:10 a.m.
NEDg Description generation batch_6a47613ffb3c81908e07e14c3a80ccb7 completed July 3, 2026, 7:14 a.m.
NED2 Entity disambiguation (via description) batch_6a4761bac97881908bf4eed576628d65 completed July 3, 2026, 7:16 a.m.
Created at: May 3, 2026, 4:04 p.m.