Triple
T12635167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin, Connecticut |
E301742
|
entity |
| Predicate | stateCode |
P20781
|
FINISHED |
| Object | CT |
E63369
|
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: [Franklin, Connecticut, stateCode, CT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CT Context triple: [Franklin, Connecticut, stateCode, 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 commonly used abbreviation for the Coral Triangle, a marine region in the western Pacific renowned as the global center of marine biodiversity.
-
C.
CT
chosen
CT is the official two-letter United States Postal Service abbreviation for the state of Connecticut.
-
D.
CT
CT is the vehicle registration code used on license plates for vehicles registered in Cetinje, Montenegro.
-
E.
CT
CT is the postcode area covering Canterbury and surrounding parts of east Kent in southeastern England.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9610fab488190ac6e6d5cf056ae37 |
completed | April 10, 2026, 8:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6719886708190823f6f7e94e4d199 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:16 p.m.