Triple

T24605932
Position Surface form Disambiguated ID Type / Status
Subject East Leake E608969 entity
Predicate hasRoadConnection P385 FINISHED
Object A6006 road
The A6006 road is a regional route in England that links several towns and villages in the East Midlands, providing an important connection between local communities and major highways.
E2295183 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: A6006 road | Statement: [East Leake, hasRoadConnection, A6006 road]
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: A6006 road
Triple: [East Leake, hasRoadConnection, A6006 road]
Generated description
The A6006 road is a regional route in England that links several towns and villages in the East Midlands, providing an important connection between local communities and major highways.

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_69e2c4d060e08190ac9f7c49b1036e20 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2aa2e74f4819086e1c8abf6f2da17 completed April 30, 2026, 1:02 a.m.
NED1 Entity disambiguation (via context triple) batch_6a7d16e55a288190bfcb51cee99a5e57 completed Aug. 13, 2026, 12:59 a.m.
NEDg Description generation batch_6a7d179823748190ba9c1cdb1b772ca1 completed Aug. 13, 2026, 1:02 a.m.
NED2 Entity disambiguation (via description) batch_6a7d17fefb888190b06d460eba5cff1c completed Aug. 13, 2026, 1:03 a.m.
Created at: April 18, 2026, 2:31 a.m.