Triple

T37437869
Position Surface form Disambiguated ID Type / Status
Subject Autoroute A104 E930327 entity
Predicate hasJunctionWith P1018 FINISHED
Object A15 near Pierrelaye
A15 near Pierrelaye is a section of the French A15 motorway in the Val-d'Oise department, serving as a key connector for traffic northwest of Paris.
E2226651 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: A15 near Pierrelaye | Statement: [Autoroute A104, hasJunctionWith, A15 near Pierrelaye]
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: A15 near Pierrelaye
Triple: [Autoroute A104, hasJunctionWith, A15 near Pierrelaye]
Generated description
A15 near Pierrelaye is a section of the French A15 motorway in the Val-d'Oise department, serving as a key connector for traffic northwest of Paris.

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_69f76ebfdcb8819098562ff3db673b04 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb8dd8b240819083a4c46abff28128 completed May 6, 2026, 6:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40825903cc819087869ea4ee185f23 completed June 28, 2026, 2:09 a.m.
NEDg Description generation batch_6a40838274448190936f743e0b1d2968 completed June 28, 2026, 2:14 a.m.
NED2 Entity disambiguation (via description) batch_6a4083ea13848190a9613bac95ba91ee completed June 28, 2026, 2:16 a.m.
Created at: May 3, 2026, 4:17 p.m.