Triple
T4925976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF postcode area |
E110575
|
entity |
| Predicate | postalAreaCode |
P222
|
FINISHED |
| Object | CF |
E110575
|
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: CF | Statement: [CF postcode area, postalAreaCode, CF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CF Context triple: [CF postcode area, postalAreaCode, CF]
-
A.
CF
CF is the two-letter ISO 3166-1 alpha-2 country code assigned to the Central African Republic.
-
B.
CF
CF is the commonly used abbreviation for the Swiss Federal Council, the collective head of state and government of Switzerland.
-
C.
CF
CF is the abbreviation for the Commonwealth Foundation, an intergovernmental organization that supports civil society and promotes democracy and development across the Commonwealth.
-
D.
CF
chosen
CF is a UK postcode area covering Cardiff and surrounding parts of South Wales, including the Vale of Glamorgan.
-
E.
FC
FC is the standard abbreviation for Fibre Channel, a high-speed network technology primarily used to connect computer data storage in storage area networks.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd7033c430819088e62f14979aa83c |
completed | March 20, 2026, 4:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be77a9dff481908c7f525f233d9bce |
completed | March 21, 2026, 10:49 a.m. |
Created at: March 20, 2026, 1:30 p.m.