Triple
T16015963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Exception |
E388466
|
entity |
| Predicate | distributor |
P1951
|
FINISHED |
| Object | A24 |
E115987
|
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: A24 | Statement: [The Exception, distributor, A24]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A24 Context triple: [The Exception, distributor, A24]
-
A.
A24
A24 is a major road designation used in several countries, typically referring to important regional or intercity routes.
-
B.
A24
chosen
A24 is an independent entertainment company known for producing and distributing critically acclaimed and distinctive films and television series.
-
C.
A244
The A244 is a regional road in England that provides a key route connecting towns in Surrey and southwest London.
-
D.
A240
The A240 is a primary road in Surrey, England, connecting Epsom to Kingston upon Thames and serving as a key local commuter route.
-
E.
A204
The A204 is a key urban road in London that serves as one of the main routes running through the Brixton area.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e18294f6c48190ab9d3eead268f846 |
completed | April 17, 2026, 12:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf284fa481909b571d1bf107fca4 |
completed | May 10, 2026, 12:19 a.m. |
Created at: April 10, 2026, 4:55 a.m.