Triple

T32201587
Position Surface form Disambiguated ID Type / Status
Subject Avening, Gloucestershire, England E822552 entity
Predicate locatedOn P40 FINISHED
Object Avening Stream
Avening Stream is a small watercourse in Gloucestershire, England, that flows through the village of Avening and forms part of the local rural landscape.
E2017541 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: Avening Stream | Statement: [Avening, Gloucestershire, England, locatedOn, Avening Stream]
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: Avening Stream
Triple: [Avening, Gloucestershire, England, locatedOn, Avening Stream]
Generated description
Avening Stream is a small watercourse in Gloucestershire, England, that flows through the village of Avening and forms part of the local rural landscape.

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_69f349093174819086e633c190a51aa8 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bb3c8d7081909b960e469e4d8504 completed May 3, 2026, 3:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a349281dd30819083b52afd95481c6f completed June 19, 2026, 12:51 a.m.
NEDg Description generation batch_6a3493a36e808190bbbfe3ad8dd86e7a completed June 19, 2026, 12:56 a.m.
NED2 Entity disambiguation (via description) batch_6a34947b6c5c8190beb4bdce0fe9e238 completed June 19, 2026, 12:59 a.m.
Created at: May 1, 2026, 12:36 a.m.