Triple
T30342561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | color video tape recorder |
E771795
|
entity |
| Predicate | recordsFrom |
P117068
|
FINISHED |
| Object | television broadcasts |
—
|
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: television broadcasts | Statement: [color video tape recorder, recordsFrom, television broadcasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsFrom Context triple: [color video tape recorder, recordsFrom, television broadcasts]
-
A.
recordsWith
Indicates that one entity keeps or maintains documented information about another entity or event.
-
B.
recordsType
Indicates that one entity documents, stores, or keeps an official account of a particular type or category of information, event, or item.
-
C.
recordsObject
Indicates that one entity creates or maintains a record of another entity as its subject or content.
-
D.
recordingsFrom
chosen
Indicates a relationship where one entity serves as the source or origin of recordings that are associated with or derived from it.
-
E.
reRecordedFrom
Indicates that one recording is a new recording derived from, based on, or made again from an earlier recording.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 29, 2026, 7:55 p.m.