Triple
T2214767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Expectations |
E48000
|
entity |
| Predicate | hasGenreScope |
P36845
|
FINISHED |
| Object | various film genres |
—
|
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: various film genres | Statement: [Great Expectations, hasGenreScope, various film genres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreScope Context triple: [Great Expectations, hasGenreScope, various film genres]
-
A.
hasGenreStrength
Indicates that something possesses a particular intensity or degree of emphasis associated with a specific genre.
-
B.
genreRestriction
Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
-
C.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
D.
hasGenreArtist
Indicates that an artist is associated with or specializes in a particular genre.
-
E.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
- F. None of above. chosen
Provenance (4 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbfef875c8190b642736b4cc11d4c |
completed | March 7, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69abbdaa26d48190860c33fd464c4845 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf0c2b8881908553eed5be17a9c2 |
completed | March 7, 2026, 6 a.m. |
Created at: March 4, 2026, 7:46 p.m.