Triple
T15465348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welcome to Wrexham |
E372017
|
entity |
| Predicate | originalNetwork |
P2594
|
FINISHED |
| Object | FX |
E69019
|
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: FX | Statement: [Welcome to Wrexham, originalNetwork, FX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FX Context triple: [Welcome to Wrexham, originalNetwork, FX]
-
A.
FX
chosen
FX is an American cable television network known for airing edgy, critically acclaimed original series and dramas.
-
B.
FX
FX is the identifying squadron code historically used by No. 92 Squadron of the Royal Air Force.
-
C.
FIN
FIN is the commonly used abbreviation for the Department of Finance Canada, the federal government department responsible for developing economic, fiscal, and tax policy.
-
D.
FIN
FIN is the three-letter ISO 3166-1 alpha-3 country code that uniquely identifies Finland in international standards and data systems.
-
E.
FIN
FIN is the three-letter station code used by London Underground to identify Finchley Road station on the Metropolitan and Jubilee lines.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d01a23c819095cf75b7d5a801a9 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:33 a.m.