Triple
T38484669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ústřední půjčovna filmů |
E917881
|
entity |
| Predicate | handledContent |
P71354
|
FINISHED |
| Object | Czechoslovak feature films |
—
|
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: Czechoslovak feature films | Statement: [Ústřední půjčovna filmů, handledContent, Czechoslovak feature films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handledContent Context triple: [Ústřední půjčovna filmů, handledContent, Czechoslovak feature films]
-
A.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
-
B.
handledIn
Indicates that an action, request, or process is managed, processed, or resolved within a particular context, location, system, or jurisdiction.
-
C.
handledMatter
chosen
Indicates that an entity has dealt with, managed, or taken responsibility for a particular matter, issue, or case.
-
D.
handledLanguage
Indicates that an entity has processed, used, or otherwise dealt with a particular language in some context.
-
E.
handlingProperty
Indicates that one entity specifies how another entity should be handled, processed, or treated under certain conditions.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.