Triple

T20907398
Position Surface form Disambiguated ID Type / Status
Subject Neu-Isenburg E514837 entity
Predicate hasTransportConnection P845 FINISHED
Object A661 motorway
The A661 motorway is a German autobahn in the state of Hesse that serves as a key regional bypass and connector around Frankfurt am Main and its surrounding towns.
E1683166 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: A661 motorway | Statement: [Neu-Isenburg, hasTransportConnection, A661 motorway]
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: A661 motorway
Triple: [Neu-Isenburg, hasTransportConnection, A661 motorway]
Generated description
The A661 motorway is a German autobahn in the state of Hesse that serves as a key regional bypass and connector around Frankfurt am Main and its surrounding towns.

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_69e0b4f8a1108190bce3d31331290ced completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6e900ee7881909ab1046b40dca486 completed April 21, 2026, 3:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad18b43c8190bd2eb11a39566ed1 completed May 22, 2026, 7:23 p.m.
NEDg Description generation batch_6a10adf21b3c8190a7388b1a74faf65e completed May 22, 2026, 7:26 p.m.
NED2 Entity disambiguation (via description) batch_6a10af719e6c8190bbd23598b3426106 completed May 22, 2026, 7:33 p.m.
Created at: April 16, 2026, 12:47 p.m.