Triple

T13312715
Position Surface form Disambiguated ID Type / Status
Subject arrondissement of Rouen E317110 entity
Predicate contains P35 FINISHED
Object Maromme E1017488 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: Maromme | Statement: [arrondissement of Rouen, contains, Maromme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maromme
Context triple: [arrondissement of Rouen, contains, Maromme]
  • A. Maromme chosen
    Maromme is a small commune in the Normandy region of northern France, located near Rouen.
  • B. Rommen
    Rommen is a neighborhood in Oslo, Norway, situated within the Søndre Nordstrand borough.
  • C. Morhaime
    Morhaime is the surname of Michael Morhaime, the American video game developer best known as the co-founder and former president of Blizzard Entertainment.
  • D. Yatomi
    Yatomi is a city in central Japan known for its location in Aichi Prefecture and its role as a local residential and agricultural community.
  • E. Shomushon
    Shomushon is the main settlement and administrative center of the Northern Islands Municipality in the Northern Mariana Islands.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d806b40ab4819094adf6c374f4811a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d990f6d34c8190ba19dc2df7d42c22 completed April 11, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69f716e7b9a48190a33b04df8ad45ed8 completed May 3, 2026, 9:35 a.m.
Created at: April 9, 2026, 9:29 p.m.