Triple
T9298992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casino Royale (1954 TV production) |
E223711
|
entity |
| Predicate | hasArchiveStatus |
P52826
|
FINISHED |
| Object | kinescope recording survives |
—
|
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: kinescope recording survives | Statement: [Casino Royale (1954 TV production), hasArchiveStatus, kinescope recording survives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchiveStatus Context triple: [Casino Royale (1954 TV production), hasArchiveStatus, kinescope recording survives]
-
A.
archivesStatus
chosen
Indicates the current archival state or condition assigned to an item, such as whether it is archived, active, or pending archiving.
-
B.
hasNotableArchive
Indicates that an entity maintains or is associated with an archive that is considered significant or noteworthy.
-
C.
archivesHeldBy
Indicates that archival materials or records are kept, managed, or preserved by a particular entity.
-
D.
hasDigitalArchive
Indicates that an entity maintains or is associated with a collection of materials stored in a digital archive.
-
E.
hasReserveStatus
Indicates that an entity holds a designated reserve or backup status in relation to another entity or role.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08cf50cc8190a025f478dff4f9fd |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.