Triple

T30021184
Position Surface form Disambiguated ID Type / Status
Subject Boulevard du Temple E762743 entity
Predicate hasPublicTransport P1288 FINISHED
Object Oberkampf metro station
Oberkampf metro station is a Paris Métro station in the 11th arrondissement, serving lines 5 and 9 near the Oberkampf and République areas.
E1937793 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: Oberkampf metro station | Statement: [Boulevard du Temple, hasPublicTransport, Oberkampf metro station]
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: Oberkampf metro station
Triple: [Boulevard du Temple, hasPublicTransport, Oberkampf metro station]
Generated description
Oberkampf metro station is a Paris Métro station in the 11th arrondissement, serving lines 5 and 9 near the Oberkampf and République areas.

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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f67987d8548190ad2276a4bc4c7a10 completed May 2, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28e43ffb288190b6391ce1031e03a2 completed June 10, 2026, 4:12 a.m.
NEDg Description generation batch_6a28e619fb9481908f6b31ee1592fd91 completed June 10, 2026, 4:20 a.m.
NED2 Entity disambiguation (via description) batch_6a28e6778d5c81908c616bd5b4b0701c completed June 10, 2026, 4:22 a.m.
Created at: April 29, 2026, 6:47 p.m.