Triple
T21223442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Competition |
E523026
|
entity |
| Predicate | hasThemeScope |
P6142
|
FINISHED |
| Object | world cinema |
—
|
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: world cinema | Statement: [International Competition, hasThemeScope, world cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThemeScope Context triple: [International Competition, hasThemeScope, world cinema]
-
A.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
C.
containsThemeArea
chosen
Indicates that one entity includes or encompasses a specific thematic area as part of its scope or content.
-
D.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
E.
hasRepresentationScope
Indicates that something is represented, described, or modeled only within a specified scope, context, or domain.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a846d08190a5470298a3ddd0f8 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.