Triple

T37624295
Position Surface form Disambiguated ID Type / Status
Subject A13 at Sadlers Farm E936159 entity
Predicate connectsDirectionFromA130 P82340 FINISHED
Object A12 corridor
The A12 corridor is a major transport route in eastern England, linking London with Essex and Suffolk and serving as a key arterial road for regional and long-distance traffic.
E2236051 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: A12 corridor | Statement: [A13 at Sadlers Farm, connectsDirectionFromA130, A12 corridor]
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: A12 corridor
Triple: [A13 at Sadlers Farm, connectsDirectionFromA130, A12 corridor]
Generated description
The A12 corridor is a major transport route in eastern England, linking London with Essex and Suffolk and serving as a key arterial road for regional and long-distance traffic.

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_69f76ed24820819081bafd36e9088701 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fff7e89b6081909f878a6c66fc40d7 completed May 10, 2026, 3:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a40afef47648190bc6d02752ca187f8 completed June 28, 2026, 5:23 a.m.
NEDg Description generation batch_6a40b16a68c08190ae4204e7cf4cdf68 completed June 28, 2026, 5:30 a.m.
NED2 Entity disambiguation (via description) batch_6a40b204c12c819085dadeffc57aa2d4 completed June 28, 2026, 5:32 a.m.
Created at: May 3, 2026, 4:18 p.m.