Triple

T4718530
Position Surface form Disambiguated ID Type / Status
Subject Clerkenwell E104706 entity
Predicate postalDistrict P920 FINISHED
Object EC1 E375865 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: EC1 | Statement: [Clerkenwell, postalDistrict, EC1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: EC1
Context triple: [Clerkenwell, postalDistrict, EC1]
  • A. EC4
    EC4 is a central London postcode district covering parts of the City of London, including key financial and commercial areas around Cannon Street and St Paul’s.
  • B. EC
    EC is the commonly used abbreviation for the World Meteorological Organization’s Executive Council, its principal governing body responsible for coordinating international meteorological activities and policies.
  • C. EC
    EC is the two-letter ISO 3166-1 alpha-2 country code assigned to Ecuador.
  • D. EC chosen
    EC is a central London postcode area covering much of the historic City of London and parts of the surrounding financial district.
  • E. EC
    EC is the student nickname for MIT’s East Campus undergraduate dormitory, known for its tight-knit, hands-on, and hacker-oriented culture.
  • 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_69bd43ec4a348190bc41afae43375e71 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd642779a08190b01e588d515cf498 completed March 20, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be108bc0048190aeea8674f75105e5 completed March 21, 2026, 3:29 a.m.
Created at: March 20, 2026, 1:18 p.m.