Triple

T17070236
Position Surface form Disambiguated ID Type / Status
Subject Miromesnil E414196 entity
Predicate hasAccessTo P1017 FINISHED
Object Rue de Penthièvre
Rue de Penthièvre is a street in Paris’s 8th arrondissement, known for its central location near major boulevards and a mix of offices, boutiques, and Haussmann-era buildings.
E2004861 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: Rue de Penthièvre | Statement: [Miromesnil, hasAccessTo, Rue de Penthièvre]
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: Rue de Penthièvre
Triple: [Miromesnil, hasAccessTo, Rue de Penthièvre]
Generated description
Rue de Penthièvre is a street in Paris’s 8th arrondissement, known for its central location near major boulevards and a mix of offices, boutiques, and Haussmann-era buildings.

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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbbfb1f08190807301ff6e573cf5 completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a33e87380b081908b73a1664aad437e completed June 18, 2026, 12:45 p.m.
NEDg Description generation batch_6a33ec5978f48190bc071890e348dbac completed June 18, 2026, 1:02 p.m.
NED2 Entity disambiguation (via description) batch_6a3449bf8fbc8190bc342a6ab2a03dca completed June 18, 2026, 7:40 p.m.
Created at: April 10, 2026, 5:34 a.m.