Triple

T31513752
Position Surface form Disambiguated ID Type / Status
Subject Alcabideche E804011 entity
Predicate hasRoadConnection P385 FINISHED
Object A16 motorway
The A16 motorway is a Portuguese highway that serves the Lisbon metropolitan area, linking coastal and inland suburbs and providing an important bypass route around the city.
E2296872 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: A16 motorway | Statement: [Alcabideche, hasRoadConnection, A16 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: A16 motorway
Triple: [Alcabideche, hasRoadConnection, A16 motorway]
Generated description
The A16 motorway is a Portuguese highway that serves the Lisbon metropolitan area, linking coastal and inland suburbs and providing an important bypass route around the city.

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_69f348ceb0a48190ae7feca263b6296c completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a2567f9c8190989b6106f8d86a9e completed May 3, 2026, 1:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a82cbac7a3c8190a121e191a4055519 completed Aug. 17, 2026, 8:51 a.m.
NEDg Description generation batch_6a82cbf78d308190b571b1dac689635a completed Aug. 17, 2026, 8:53 a.m.
NED2 Entity disambiguation (via description) batch_6a82cc4c82148190830f2b3990c7bfc5 completed Aug. 17, 2026, 8:54 a.m.
Created at: April 30, 2026, 9:51 p.m.