Triple

T30984858
Position Surface form Disambiguated ID Type / Status
Subject South Ferriby E789492 entity
Predicate locatedEastOf P4240 FINISHED
Object South Cave (across Humber)
South Cave (across Humber) is a village in the East Riding of Yorkshire, England, situated near the north bank of the Humber Estuary.
E1941178 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: South Cave (across Humber) | Statement: [South Ferriby, locatedEastOf, South Cave (across Humber)]
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: South Cave (across Humber)
Triple: [South Ferriby, locatedEastOf, South Cave (across Humber)]
Generated description
South Cave (across Humber) is a village in the East Riding of Yorkshire, England, situated near the north bank of the Humber Estuary.

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_69f224c550b081909ddfceb0c3d03bdd completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f693c1b9f88190a439254f342c1679 completed May 3, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a28fbc393a081908a73cc1d3b6cd7a3 completed June 10, 2026, 5:53 a.m.
NEDg Description generation batch_6a28fd4d08508190985f0cf9662da106 completed June 10, 2026, 5:59 a.m.
NED2 Entity disambiguation (via description) batch_6a290155e22081909ec5bb8db128331e completed June 10, 2026, 6:16 a.m.
Created at: April 29, 2026, 8:56 p.m.