Triple

T24617637
Position Surface form Disambiguated ID Type / Status
Subject Wenvoe E609308 entity
Predicate hasNearbySettlement P4647 FINISHED
Object Culverhouse Cross
Culverhouse Cross is a major road junction and commercial area on the western outskirts of Cardiff, Wales, known for its retail parks and strategic position on key regional routes.
E1645384 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: Culverhouse Cross | Statement: [Wenvoe, hasNearbySettlement, Culverhouse Cross]
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: Culverhouse Cross
Triple: [Wenvoe, hasNearbySettlement, Culverhouse Cross]
Generated description
Culverhouse Cross is a major road junction and commercial area on the western outskirts of Cardiff, Wales, known for its retail parks and strategic position on key regional routes.

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_69e2c4d1140081909c58667bf68f80c3 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2aa6317ec81909144992a29dd81c0 completed April 30, 2026, 1:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10047fab9c81909558ceb6239f5ed5 completed May 22, 2026, 7:23 a.m.
NEDg Description generation batch_6a100a1280fc8190ae7931526b0ddc97 completed May 22, 2026, 7:47 a.m.
NED2 Entity disambiguation (via description) batch_6a100a6f955081908f3536c15b2a44a9 completed May 22, 2026, 7:49 a.m.
Created at: April 18, 2026, 2:31 a.m.