Triple
T34946061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovak Television |
E1007858
|
entity |
| Predicate | archivalHolder |
P39745
|
FINISHED |
| Object | Czech Television archives |
—
|
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: Czech Television archives | Statement: [Czechoslovak Television, archivalHolder, Czech Television archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archivalHolder Context triple: [Czechoslovak Television, archivalHolder, Czech Television archives]
-
A.
archivesHeldBy
chosen
Indicates that archival materials or records are kept, managed, or preserved by a particular entity.
-
B.
archivesHeldIn
Indicates that archival materials or records are stored, maintained, or preserved at a specified location or institution.
-
C.
archiveHoldingPrint
Indicates that an archive or repository possesses and maintains a physical (print) copy of a specified item.
-
D.
archiveOf
Indicates that one entity serves as a stored collection or repository preserving the records, documents, or materials of another entity.
-
E.
archiveFor
Indicates that one entity serves as a storage or preservation repository specifically for the records, documents, or data of another entity.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4 p.m.