Triple
T20020870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creg-ny-Baa |
E494851
|
entity |
| Predicate | isFilmedFor |
P50244
|
FINISHED |
| Object | onboard TT race coverage |
—
|
LITERAL 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: onboard TT race coverage | Statement: [Creg-ny-Baa, isFilmedFor, onboard TT race coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFilmedFor Context triple: [Creg-ny-Baa, isFilmedFor, onboard TT race coverage]
-
A.
filmedFor
chosen
Indicates that something was recorded or produced specifically for a particular purpose, audience, platform, or project.
-
B.
filmedAs
Indicates that an entity was recorded or captured in a particular form, version, or role during a filming or production process.
-
C.
filmedFrom
Indicates that one entity serves as the physical or conceptual vantage point or recording source from which another entity (such as a scene, object, or event) is filmed.
-
D.
wasRecordedIn
Indicates that an event, action, or piece of information was documented or captured within a specific record, medium, or recording session.
-
E.
recordedForFilm
Indicates that an audio or performance was captured specifically for use in a film production.
- F. None of above.
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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623fe1988190a1c09d392d866dc8 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.