Triple
T33956351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rallycross |
E870581
|
entity |
| Predicate | firstTelevisedIn |
P205261
|
FINISHED |
| Object | United Kingdom |
E732
|
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: United Kingdom | Statement: [Rallycross, firstTelevisedIn, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTelevisedIn Context triple: [Rallycross, firstTelevisedIn, United Kingdom]
-
A.
firstTelecastOn
Indicates the date or event on which something, typically a program or broadcast, was first shown on television.
-
B.
firstAppearanceTV
Indicates the television show or episode in which an entity is depicted or mentioned for the first time.
-
C.
firstTelevisionProgram
Indicates that the subject entity is the earliest or initial television program associated with the object entity (such as a person, channel, or series).
-
D.
firstTelevisionBroadcast
Indicates that the subject is the entity responsible for the earliest or inaugural television broadcast of the object.
-
E.
firstBroadcastSeries
Indicates that one series was the first to be broadcast within a particular context, channel, or sequence of series.
- F. None of above. chosen
Provenance (5 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370da2bdb88190b7cfae3442d9ec98 |
completed | June 20, 2026, 10:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:49 a.m.