Triple

T22013749
Position Surface form Disambiguated ID Type / Status
Subject Chermayeff & Geismar E543648 entity
Predicate notableClient P7186 FINISHED
Object Mobil 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: Mobil | Statement: [Chermayeff & Geismar, notableClient, Mobil]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mobil
Context triple: [Chermayeff & Geismar, notableClient, Mobil]
  • A. Mobil chosen
    Mobil is a major American oil company and fuel brand that became part of ExxonMobil after a 1999 merger.
  • B. Mobilis
    Mobilis is the integrated public transport fare network for the canton of Vaud in Switzerland, covering multiple operators and modes of transport under a unified ticketing system.
  • C. Benz
    Benz is a German surname most famously associated with automotive pioneer Karl Benz and the Mercedes-Benz brand.
  • D. Fordon
    Fordon is a large residential and industrial district of Bydgoszcz in northern Poland, known for its post-war housing estates and location along the Vistula River.
  • E. Mobilong
    Mobilong is a locality in South Australia situated near the Murray River within the Rural City of Murray Bridge.
  • 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_69e11e2db934819095556760c7d85e4d completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127a6bf6081909865781ea7937a1b completed April 28, 2026, 9:33 p.m.
Created at: April 16, 2026, 8:22 p.m.