Triple
T13581146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Cottrell-Boyce |
E324418
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object | Code 46 |
E322869
|
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: Code 46 | Statement: [Frank Cottrell-Boyce, notableWork, Code 46]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Code 46 Context triple: [Frank Cottrell-Boyce, notableWork, Code 46]
-
A.
Code 46
chosen
Code 46 is a 2003 dystopian science fiction film blending romance and bioethics, written by Frank Cottrell-Boyce and directed by Michael Winterbottom.
-
B.
CPC464
The CPC464 is an 8-bit home computer released by Amstrad in 1984, notable for its built-in cassette deck and popularity in the European home computing market.
-
C.
S46
S46 is a commuter rail line of the Berlin S-Bahn network serving suburban and urban areas along its designated route.
-
D.
A46
A46 is a major trunk road in England that runs from Bath in the southwest to Cleethorpes on the east coast, connecting several key cities and regions.
-
E.
Line 46
Line 46 is a planned rapid transit line of the Shenzhen Metro system in Shenzhen, China.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb031e8048190a5f2ea934308036c |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bbdb2d0819089f094e57dde28cf |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.