Triple
T5514005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armchair Theatre |
E144636
|
entity |
| Predicate | laterRecordedOn |
P28321
|
FINISHED |
| Object | videotape |
—
|
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: videotape | Statement: [Armchair Theatre, laterRecordedOn, videotape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRecordedOn Context triple: [Armchair Theatre, laterRecordedOn, videotape]
-
A.
laterRecordedIn
chosen
Indicates that the referenced information or event was documented or captured at a later time in the specified source or record.
-
B.
laterRecordedBy
Indicates that the subject work or version was recorded at a later time by the specified artist or entity.
-
C.
recordedFor
Indicates that something has been documented, captured, or logged on behalf of or in association with a particular entity or context.
-
D.
originallyRecordedFor
Indicates that a work or performance was first recorded with the specific purpose of being used, released, or presented in the context of the target entity.
-
E.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
- 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_69c008f77ff88190b0cd50ca207295d1 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f5b4e988190b590b4157cf089c1 |
completed | March 22, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:33 p.m.