Triple

T26790718
Position Surface form Disambiguated ID Type / Status
Subject Crampton’s Gap E670509 entity
Predicate namedAfter P63 FINISHED
Object Crampton family (local landowners)
The Crampton family were prominent local landowners whose name was given to Crampton’s Gap, reflecting their historical influence in the area.
E1742420 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: Crampton family (local landowners) | Statement: [Crampton’s Gap, namedAfter, Crampton family (local landowners)]
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: Crampton family (local landowners)
Triple: [Crampton’s Gap, namedAfter, Crampton family (local landowners)]
Generated description
The Crampton family were prominent local landowners whose name was given to Crampton’s Gap, reflecting their historical influence in the area.

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_69eeb31d45f8819089f52ebdbc556218 completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f619baac9c8190afeb5089b347e74b completed May 2, 2026, 3:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a120964970c8190826373f6dbd1afdc completed May 23, 2026, 8:09 p.m.
NEDg Description generation batch_6a120aa69a8c819083a6dc95e4d6382e completed May 23, 2026, 8:14 p.m.
NED2 Entity disambiguation (via description) batch_6a120b39cddc8190a6c89274fc238b1a completed May 23, 2026, 8:16 p.m.
Created at: April 27, 2026, 4:16 a.m.