Triple
T23878049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golan-Globus Productions |
E600120
|
entity |
| Predicate | notableProductionStyle |
P46117
|
FINISHED |
| Object | exploitation marketing |
—
|
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: exploitation marketing | Statement: [Golan-Globus Productions, notableProductionStyle, exploitation marketing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProductionStyle Context triple: [Golan-Globus Productions, notableProductionStyle, exploitation marketing]
-
A.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
B.
notableProductionType
chosen
Indicates that the subject is particularly known for producing or creating instances of the specified type.
-
C.
notableSeriesStyle
Indicates that a work is created in the characteristic style of a notable series or franchise.
-
D.
notableStyleFeature
Indicates that an entity possesses a distinctive stylistic characteristic or design element that is especially noteworthy or defining.
-
E.
notableSubstyle
Indicates that one style is a notable or distinct subcategory within another broader style.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc032c9c81909986ae6f672c1ad1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:23 p.m.