Triple
T7611189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CT postcode area |
E172239
|
entity |
| Predicate | hasPostcodeDistrict |
P961
|
FINISHED |
| Object |
CT1
CT1 is a central Canterbury postcode district in the CT area of southeast England, covering much of the historic city and its immediate surroundings.
|
E676561
|
NE FINISHED |
How this triple was built (4 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: CT1 | Statement: [CT postcode area, hasPostcodeDistrict, CT1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CT1 Context triple: [CT postcode area, hasPostcodeDistrict, CT1]
-
A.
CT1
CT1 is a 3GPP working group responsible for specifying core network and terminal aspects of mobile telecommunications systems.
-
B.
CT 15
CT 15 is a major limited-access highway in Connecticut, best known for including the historic Merritt Parkway and Wilbur Cross Parkway corridors.
-
C.
CTN
CTN is the ICAO airline designator used to identify Croatia Airlines in international aviation operations.
-
D.
CT3
CT3 is a 3GPP Core Network and Terminals working group responsible for developing and maintaining signaling protocols and related specifications for mobile telecommunications networks.
-
E.
CT4
CT4 is a 3GPP working group responsible for specifying protocols and interfaces for core network and terminal interoperability in mobile telecommunications systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: CT1 Triple: [CT postcode area, hasPostcodeDistrict, CT1]
Generated description
CT1 is a central Canterbury postcode district in the CT area of southeast England, covering much of the historic city and its immediate surroundings.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: CT1 Target entity description: CT1 is a central Canterbury postcode district in the CT area of southeast England, covering much of the historic city and its immediate surroundings.
-
A.
CT1
CT1 is a 3GPP working group responsible for specifying core network and terminal aspects of mobile telecommunications systems.
-
B.
CT 15
CT 15 is a major limited-access highway in Connecticut, best known for including the historic Merritt Parkway and Wilbur Cross Parkway corridors.
-
C.
CTN
CTN is the ICAO airline designator used to identify Croatia Airlines in international aviation operations.
-
D.
CT3
CT3 is a 3GPP Core Network and Terminals working group responsible for developing and maintaining signaling protocols and related specifications for mobile telecommunications networks.
-
E.
CT4
CT4 is a 3GPP working group responsible for specifying protocols and interfaces for core network and terminal interoperability in mobile telecommunications systems.
- F. None of above. chosen
Provenance (5 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_69c6994f50808190ba228764bb422417 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa221c848190b892ba1caec8d83a |
completed | March 27, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c868645f8081909439f63df3184628 |
completed | March 28, 2026, 11:46 p.m. |
| NEDg | Description generation | batch_69c868edf84c8190a6fefce18fc606e1 |
completed | March 28, 2026, 11:49 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c869c54ad08190ba42231080d0e9f3 |
completed | March 28, 2026, 11:52 p.m. |
Created at: March 27, 2026, 3:55 p.m.