Triple

T19053990
Position Surface form Disambiguated ID Type / Status
Subject San Fernando de Henares E466341 entity
Predicate roadServedBy P385 FINISHED
Object M-50 motorway
The M-50 motorway is a major orbital ring road around Madrid, Spain, designed to divert traffic from the city center and connect key radial highways and suburbs.
E2221303 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: M-50 motorway | Statement: [San Fernando de Henares, roadServedBy, M-50 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: M-50 motorway
Triple: [San Fernando de Henares, roadServedBy, M-50 motorway]
Generated description
The M-50 motorway is a major orbital ring road around Madrid, Spain, designed to divert traffic from the city center and connect key radial highways and suburbs.

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_69d8dd040fb881909af2a964f65ad208 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5dc049f64819093ae9fda26a49bd2 completed April 20, 2026, 7:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a405108e5c881908ebf0bf830d3e152 completed June 27, 2026, 10:39 p.m.
NEDg Description generation batch_6a4052b333488190a052c6d088fa5e90 completed June 27, 2026, 10:46 p.m.
NED2 Entity disambiguation (via description) batch_6a40547b53508190a42111bd8ad75a9a completed June 27, 2026, 10:53 p.m.
Created at: April 10, 2026, 12:03 p.m.