Triple

T13061488
Position Surface form Disambiguated ID Type / Status
Subject Stourmouth E329207 entity
Predicate hasPostcodeArea P920 FINISHED
Object CT E172239 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: CT | Statement: [Stourmouth, hasPostcodeArea, CT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CT
Context triple: [Stourmouth, hasPostcodeArea, CT]
  • A. CT
    CT is a 3GPP core network and terminals working group responsible for specifying protocols and interfaces for mobile telecommunications systems.
  • B. CT
    CT is the official two-letter United States Postal Service abbreviation for the state of Connecticut.
  • C. CT
    CT is the commonly used abbreviation for the Coral Triangle, a marine region in the western Pacific renowned as the global center of marine biodiversity.
  • D. CT chosen
    CT is the postcode area covering Canterbury and surrounding parts of east Kent in southeastern England.
  • E. CT
    CT is the vehicle registration code used on license plates for vehicles registered in Cetinje, Montenegro.
  • 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_69d80771749c81909a6d9197b9504872 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980e7ee548190b4b18bdb1357c359 completed April 10, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6d6016984819097c999772db1e831 completed May 3, 2026, 4:58 a.m.
Created at: April 9, 2026, 8:59 p.m.