Triple

T27856147
Position Surface form Disambiguated ID Type / Status
Subject Sonning Eye E704091 entity
Predicate hasNearbyIsland P970 FINISHED
Object Sonning Eye island
Sonning Eye island is a small, picturesque island in the River Thames near the hamlet of Sonning Eye, known for its tranquil natural setting and riverside charm.
E2297471 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: Sonning Eye island | Statement: [Sonning Eye, hasNearbyIsland, Sonning Eye island]
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: Sonning Eye island
Triple: [Sonning Eye, hasNearbyIsland, Sonning Eye island]
Generated description
Sonning Eye island is a small, picturesque island in the River Thames near the hamlet of Sonning Eye, known for its tranquil natural setting and riverside charm.

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_69ef840e614c8190a88cf9638c14a265 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f63908927c81909a4637db44d91d9b completed May 2, 2026, 5:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a838944ce108190a880cac0d3df5560 completed Aug. 17, 2026, 10:20 p.m.
NEDg Description generation batch_6a8389ad8b7c81909455f2ed6e5fceaf completed Aug. 17, 2026, 10:22 p.m.
NED2 Entity disambiguation (via description) batch_6a838a108f848190aefdf113c5b84c75 completed Aug. 17, 2026, 10:24 p.m.
Created at: April 27, 2026, 6:14 p.m.