Triple

T18383348
Position Surface form Disambiguated ID Type / Status
Subject Grand-Orly Seine Bièvre E446512 entity
Predicate hasMemberMunicipality P47323 FINISHED
Object Morangis NE NERFINISHED

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: Morangis | Statement: [Grand-Orly Seine Bièvre, hasMemberMunicipality, Morangis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Morangis
Context triple: [Grand-Orly Seine Bièvre, hasMemberMunicipality, Morangis]
  • A. Morangis chosen
    Morangis is a commune in the southern suburbs of Paris, located in the Essonne department in the Île-de-France region of northern France.
  • B. Martelange
    Martelange is a small Belgian town known for straddling the border with Luxembourg and serving as a local commercial and transit hub.
  • C. Beaufays
    Beaufays is a village in the municipality of Chaudfontaine in the province of Liège, Belgium.
  • D. Fernelmont
    Fernelmont is a rural municipality in the province of Namur in Wallonia, Belgium, known for its agricultural landscape and small villages.
  • E. Rodange
    Rodange is a town in southwestern Luxembourg known as an important railway junction near the Belgian and French borders.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e5179c931c8190b1c7c8284f42f7b7 completed April 19, 2026, 5:57 p.m.
Created at: April 10, 2026, 10:45 a.m.